Broadcast event to all
Trigger a broadcast event to all existing subscribers, could be used to send announcements, etc. In the future could be used to trigger events to a subset of subscribers based on defined filters.
Authorizations
API key authentication. Allowed headers-- "Authorization: ApiKey <api_key>".
Headers
A header for idempotency purposes
Body
The trigger identifier associated for the template you wish to send. This identifier can be found on the template page.
The payload object is used to pass additional information that could be used to render the template, or perform routing rules based on it. For In-App channel, payload data are also available in <Inbox />
This could be used to override provider specific configurations
A unique identifier for this transaction, we will generated a UUID if not provided.
It 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
It is used to specify a tenant context during trigger event. If a new tenant object is provided, we will create a new tenant.
Response
Indicates whether the trigger was acknowledged or not
Status of the trigger
error
, trigger_not_active
, no_workflow_active_steps_defined
, no_workflow_steps_defined
, processed
, no_tenant_found
, invalid_recipients
In case of an error, this field will contain the error message(s)
The returned transaction ID of the trigger
Was this page helpful?