Action
Reference information about the actions entities
For bleeding edge, select "Dev", as this contains the most recent unreleased changes to the Dialogporten API. Select "Local dev" if you want to test changes to Dialogporten itself running locally.
Actions describe operations the end user or a client integration can perform in relation to a dialog.
Both GUI actions and API actions share the same core authorization model:
actionmaps to an action identifier in the service resource policy- an authorization context (preferred) can evaluate the action against a different resource, additional parties, or both
authorizationAttribute(deprecated) can override the default authorization resource for the actionisAuthorizedshows whether the authenticated user is currently authorized- when the action carries an authorization context the current user is authorized for, the dialog token lists the action’s
id(or the context’stokenRef) in itseclaim instead of adding the action to theaclaim
In end-user APIs, the URLs of an unauthorized action are masked:
- GUI action URLs are rewritten to
urn:dialogporten:unauthorized - API action endpoint URLs are rewritten to
urn:dialogporten:unauthorized
An action whose authorization context sets unauthorizedPresentation to Excluded is not masked but removed: it leaves guiActions or apiActions, and only its id and creation time appear in excludedGuiActions or excludedApiActions beside it.
GUI actions are intended for browser-based frontends and add UI-specific fields such as:
priorityhttpMethodtitle- optional
prompt isDeleteDialogAction
API actions are intended for client integrations and group one or more versioned endpoints. Each endpoint can expose:
versionurlhttpMethod- optional
documentationUrl - optional
requestSchema - optional
responseSchema deprecated- optional
sunsetAt
GUI Actions
API Actions
Read more