Delivery of event payloads after a subscription is created are billable.

Every event payload that is processed (see note below) by Tray is billed as 1 task.

Note: Processed events include:

Events that were delivered to your subscription URL successfully
Events where Tray attempted delivery but your endpoint doesn't respond after retries
Events which you filter out at the connector level e.g. applying a filter condition using pick val on salesforce 'on record create'.

Since all of the above events were processed by Tray, these will be billed.

Creates a subscription using a trigger operation and returns the `state` of subscription. The input is a regular json object that must fit the input schema of the operation as retrieved from [Get trigger operations](/developer/platform-apis/triggers#endpoint-get-trigger-operations). The authId field should be the id of a previously [created authentication](/developer/platform-apis/authentications#endpoint-create-user-authentication). The output is also a regular json object containing the response from the 3rd party. The `state` field indicates the current status of the subscription. This reqest has a 60 seconds timeout, if the subscription is created successfully within 60 seconds, you will receive a response with `active` state.

Event payload

Once a subscription is in `active` state, the events would start coming at the `endpoint` defined the request. Here is how the event payload may look like: { "id": "", "subscription": { "id": "", "externalId": "" }, "outcome": "success", "body": {}, "timestamp": "2023-04-13 10:04:00Z" } If the outcome is `success`, the `body` in the above payload would follow the Output Schema of the trigger operation.

You can visualize the sample event payloads from any Trigger in the Operations Explorer app.

If the outcome is `failure`, then manual testing with the API is required as every 3rd party service would have it's own failure responses.

Share with emails

Request Examples

Response Examples