service.ping event. With a body, you can specify the event kind and provide your own data payload to simulate a real event shape.
Request
Path parameters
The subscription ID (e.g.
sub_2QkP9aB7xN...).Body
All fields are optional. Omit the body entirely to send aservice.ping.
The event kind to simulate. Currently supported:
wallet.transfer.broadcasted, service.ping. Defaults to service.ping when omitted.Arbitrary data payload for the synthetic event. You are responsible for shaping this to match the expected event schema. Ignored when
kind is service.ping.Example 1 — send a ping
Example 2 — send a synthetic transfer event
Response
200 OK — theEventView for the test event that was queued for delivery.
The test event is queued for immediate delivery. Check your destination (e.g. webhook.site) within a few seconds to confirm receipt. If you do not see it, inspect the event’s
status, responseStatus, and responseBody fields using GET /events/:eventId.Errors
| Code | HTTP | Description |
|---|---|---|
not_found | 404 | The subscription ID does not exist or belongs to a different API key. |
unsupported_event | 400 | The kind value is not a supported event type for /test. |
unauthorized | 401 | The Authorization header is missing or the key is invalid. |