Create an Event Subscription
Create an event subscription corresponding to your Chariot account.
Request body
The webhook url where we'll send notifications.
The category of the event. This is useful for filtering events.
Event names follow the pattern {resource}.{event_type} where event_type is either created or updated. Status transitions (for example, a Donor Account moving to approved or rejected) are emitted as {resource}.updated events — fetch the object to read its current status.
The key that will be used to sign webhooks. If no value is passed, a random string will be used as default. This is necessary to verify that the webhook is coming from Chariot. While this parameter is optional, it is highly recommended to pass a value for the secret and implement webhook signature verification.
Example request
{
"url": "https://example.com/webhook"
}Response
Created
The unique identifier for the event subscription
The date and time the event subscription was created
The status of the event subscription. This indicates if we'll send notifications to this subscription
- active: subscription is active and events will be delivered normally
- disabled: subscription is temporarily disabled and events will not be delivered
- deleted: subscription has been deleted and events will not be delivered
- requires_attention: subscription has been disabled due to delivery failures and events will not be delivered
The webhook url where we'll send notifications.
The category of the event. This is useful for filtering events.
Event names follow the pattern {resource}.{event_type} where event_type is either created or updated. Status transitions (for example, a Donor Account moving to approved or rejected) are emitted as {resource}.updated events — fetch the object to read its current status.
Example response
{
"id": "4d06d393-1f14-46cf-b02d-8db17d7ed06a",
"created_at": "2024-01-14T12:48:56.37Z",
"url": "https://example.com/webhook"
}