ANanchorbrowser
Webhooks

Send Test Event

Changed on

Fire a synthetic event of the given type through the real signing + retry path. Useful during development for confirming your endpoint can verify the signature and is reachable from Anchor's egress IPs.

The synthetic delivery counts toward your delivery log so you can see it in GET /v1/webhooks/{id}/events.

post/v1/webhooks/{id}/test

Request

  • Base URL
    https://api.anchorbrowser.io
  • Auth
    API key in header anchor-api-key

Path parameters

idstring required

Webhook id.

Request body

event_type'task.completed' | 'task.failed' | 'task.cancelled' | 'task.healed' | 'session.ready' | 'session.completed' | 'session.failed' | 'session.recording.ready' | 'batch.completed' | 'batch.failed' | 'intervention.requested' | 'intervention.resolved' | 'identity.authenticated' | 'identity.authentication_failed' required

Catalog of webhook event types Anchor can deliver. Adding a new event type is a coordinated change between session-manager (publisher), webhook-dispatcher (consumer), and the dashboard.

Response

Synthetic event accepted and enqueued for delivery.

external_event_idstring required

The synthetic event id that will appear on the receiver as id in the envelope.

event_type'task.completed' | 'task.failed' | 'task.cancelled' | 'task.healed' | 'session.ready' | 'session.completed' | 'session.failed' | 'session.recording.ready' | 'batch.completed' | 'batch.failed' | 'intervention.requested' | 'intervention.resolved' | 'identity.authenticated' | 'identity.authentication_failed' required

Catalog of webhook event types Anchor can deliver. Adding a new event type is a coordinated change between session-manager (publisher), webhook-dispatcher (consumer), and the dashboard.

Example response

{
  "external_event_id": "evt_56a4c6e7f11e4b44eafce28a"
}

Changes