Skip to main content
The payload structure depends on your destination type:
  • Webhook destinations: Payloads include notificationType and data fields.
  • Kinesis destinations: Payloads contain the data object. The notificationType is included in the event metadata.
You can find the OpenAPI spec for notification payloads on GitHub, or refer to the examples below:
Some payloads may include a config field nested within the data field. This config contains the complete installation configuration, including read, write, subscribe, and proxy settings. The installation.updated event also includes an additional lastConfig field representing the previous configuration. If the configuration object is too large to include inline, we will generate a signed URL you can use to fetch full configuration via GET request as a JSON file.
Webhook destination payload:
Kinesis destination payload:
Note: config contains the complete installation configuration object including read, write, subscribe, and proxy settings. installation.updated includes an additional lastConfig field with the previous configuration.
Webhook destination payload:
Kinesis destination payload:
Webhook destination payload:
Kinesis destination payload:
Note: config contains the complete installation configuration object including read, write, subscribe, and proxy settings.
Webhook destination payload:
Kinesis destination payload:
Webhook destination payload:
Kinesis destination payload:
Webhook destination payload:
Kinesis destination payload: