Creates a single subscription. A subscription indicates which event types to receive notifications for and which callback, or webhook, to receive them on. A new subscription can take up to two minutes to become active. You can create a subscription only for a verified callback and up to 200 subscriptions per callback.
|Required. Name of the subscription. This name must be unique.
|Required. Unique identifier of the callback that receives the notification events. This callback must already exist and must be verified.
|Required. Comma-separated list of fully qualified event types for which you’re requesting notifications. Expressed as NotificationEventCategory.NotificationEventType. Review Supported Notification Events for a list of supported event categories and types.
|Each string in the array is a key
To create a subscription, send a POST request to the
The subscription you create is in active status, and event notifications are sent to the associated callback. Ensure that the callback you specify is ready to receive events before creating a subscription for it.
The response contains information about the subscription.
|Subscription is created. Review example response.
|304 No Change
|Subscription already exists on the server.
|400 Bad Request
|Failed to pass authorization.
|404 Not Found
|Callback ID doesn't exist.
|500 Server Error