Action
Reference information about the actions entities
Select environment:
Help
This dropdown lets you select which Dialogporten environment the content of this page should be based on. If unsure, use the default "Staging (TT02)", as this is the environment you would normally test against when integrating Dialogporten.
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.
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 policyauthorizationAttributecan override the default authorization resource for the actionisAuthorizedshows whether the authenticated user is currently authorized
In end-user APIs, unauthorized targets are redacted:
- GUI action URLs are rewritten to
urn:dialogporten:unauthorized - API action endpoint URLs are rewritten to
urn:dialogporten:unauthorized
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