Trigger event
Trigger event is the main (and only) way to send notifications to subscribers. The trigger identifier is used to match the particular workflow associated with it. Additional information can be passed according the body interface below.
/v1/events/trigger
Authorization
Authorization
<token>API key authentication. Allowed headers-- "Authorization: ApiKey <api_key>".
In: header
Request Body
application/json
Requiredname
RequiredstringThe trigger identifier of the workflow you wish to send. This identifier can be found on the workflow page.
payload
objectThe payload object is used to pass additional custom information that could be used to render the workflow, or perform routing rules based on it. This data will also be available when fetching the notifications feed from the API to display certain parts of the UI.
overrides
objectThis could be used to override provider specific configurations
to
Requiredarray<object | object | string> | string | object | objectThe recipients list of people who will receive the notification.
transactionId
stringA unique identifier for this transaction, we will generate a UUID if not provided.
actor
string | objectIt is used to display the Avatar of the provided actor's subscriber id or actor object. If a new actor object is provided, we will create a new subscriber in our system
tenant
string | objectIt is used to specify a tenant context during trigger event. Existing tenants will be updated with the provided details.
Header Parameters
idempotency-key
stringA header for idempotency purposes
Created