Use these operations to manage webhooks. Webhooks notify your systems in real-time when certain events occur. For example, when a new transaction occurs or a new subscription is created. Webhooks enable you to collect information about events. Rebilly can send this information by HTTP POST request to a defined URL of your choice.
Sends a test webhook.
Webhook to create or update.
Event types that trigger the webhook. If empty, all event types trigger the webhook.
Webhook request body. If this value is null, the default payload for the specified event is used. Template placeholders are permitted.
Invalid placeholders render as empty strings. For example, Hello {{invalid.placeholder}}! is rendered as Hello !.
For more information, see Placeholders.
Filter that determines whether to send the webhook. This field requires a special format. Use , for multiple allowed values. Use ; for multiple fields.
For more information, see Using filters.
- Mock serverhttps://www.rebilly.com/_mock/catalog/all/previews/webhooks
- Sandbox serverhttps://api-sandbox.rebilly.com/organizations/{organizationId}/previews/webhooks
- Live serverhttps://api.rebilly.com/organizations/{organizationId}/previews/webhooks
curl -i -X POST \
https://www.rebilly.com/_mock/catalog/all/previews/webhooks \
-H 'Content-Type: application/json' \
-H 'REB-APIKEY: YOUR_API_KEY_HERE' \
-d '{
"eventsFilter": [],
"status": "active",
"method": "GET",
"url": "http://example.com",
"headers": [
{
"name": "Content-Type",
"status": "active",
"value": "value1"
}
],
"credentialHash": "string",
"body": "string",
"filter": "string"
}'Test webhook sent.
Maximum number of requests available at one time for this rate limit. For more information, see Rate limits.
Number of requests still available for this rate limit. For more information, see Rate limits.
No content