Register a webhook
Creates a new webhook. Webhooks are registered per merchant_code and per environment:
the environment is determined by the secret key you authorize the request with —
a production key (sk_...) registers webhooks for production payments, a test key
(sk_test_...) registers webhooks for test payments. Each merchant_code + key pair
can have up to 4 webhooks.
Authorizations
Bearer authentication header of the form Bearer <secret_key>, where <secret_key> is your secret_key.
Headers
Used for multi store/countries setup, please contact your Account manager to recognize that
"code provided to you from Tabby side"
Body
Response
Success. Webhook object is returned.
Deprecated. The webhook environment is determined by the secret key used at registration (production sk_... or test sk_test_...), not by this field.
HTTPS endpoint for notifications. The URL should be valid and accessible (not local).
"https://example.com/"
Unique webhook ID, assigned by Tabby.
"unique webhook id"