Webhook notifications
Ping a subscription
POST
Ping a subscription
If you need to check the connectivity of a subscription, even if it is disabled, you can send a ping event.
To do that, you only need to
POST, with all the usual headers, the path /webhooks/ping/:subscription_id:.
This endpoint does not require a body as input and neither does it return anything: it is only a POST call that will generate a 204 response.
Calling the endpoint will generate a ping event to simulate the workflow of a regular webhook, triggering a notification for the configured URL.
The Ping webhook is a special one since it is sent to specific subscriptions.
You can expect the communication between this API and your webhook receiver to follow the same rules as other types of webhooks.
The header X-Ebury-Client-Id will be populated, and X-Ebury-Webhook will contain the special value Ping.
The payload will be a valid json without any specific schema, apart from being signed in X-Ebury-Signature as usual.