Test event (webhook.test)

Fired on demand via POST /api/v1/webhook-endpoints/{id}/test — it is not subscribable and does not appear in the subscription catalog. The delivery travels the real pipeline (queue, HMAC signature, request/response capture, retry) and is sent only to the target endpoint, regardless of the subscribed event list.

Use it to validate the consumer end to end before the first business event: signature, request authentication, envelope parsing and the fast 2xx.

webhook.test

{
  "event": "webhook.test",
  "timestamp": "2026-07-23T12:00:00.000Z",
  "organizationId": "0f7a3c1e-2b4d-4e6f-8a9b-1c2d3e4f5a6b",
  "data": {
    "test": true,
    "endpointId": "9e1f3a5b-7d2c-4e6a-8b0f-5c7e9a1d3f5b",
    "url": "https://example.com/webhooks/kobana",
    "triggeredAt": "2026-07-23T12:00:00.000Z"
  }
}

The trigger's response (202 Accepted) carries eventId and deliveryId — track the delivery via GET /api/v1/webhook-endpoints/{id}/deliveries or on the deliveries screen. If the endpoint is inactive, the trigger fails with 409 ENDPOINT_INACTIVE.

Checklist of what to validate on your side:

• The t=,v1= signature matches and t is within the tolerance (Security).
• The consumer responds 2xx in under 10 seconds.
• data.test === true is handled without side effects in your system (do not create business records from it).