Skip to main content
POST
cURL
Enqueues a real, HMAC-signed test delivery of a realistic sample payload to a webhook’s registered URL. The delivery is shaped exactly like a production event and carries "test": true in the envelope, so it never mixes with your real events. The webhook must belong to your upstream entity. Use List Webhooks to find the webhookId.

Path Parameters

Request Body

Scenario keys by webhook type

Response Shape

All successful responses are wrapped in the standard response envelope. See Request/Response Conventions.

Response Fields

The response confirms the delivery was enqueued. The actual signed POST arrives at your registered URL moments later. Inspect the delivery history in the Turris Web App to see the outcome.

Error Scenarios

Bad Request (400)

Returned when webhookId is not a valid MongoDB ObjectId, or scenario is not a valid key for the webhook’s type.

Unauthorized (401)

Missing or invalid authentication token. See Authentication.

Webhook Not Found (404)

Returned when the webhook does not exist or belongs to a different upstream entity.

Too Many Requests (429)

Returned when you exceed the test-send rate limit. Space out your test calls and retry.

Path Parameters

webhookId
string
required

Unique identifier of the webhook to test

Example:

"6650a1b2c3d4e5f6a7b8c9d0"

Body

application/json
scenario
string

Scenario key to sample. Must be a valid key for the webhook type (see the webhook type reference). Omit to use the type default.

Example:

"filed"

Response

A real signed test event was enqueued for delivery to the webhook URL

data
object
required
requestId
string
required

Unique request identifier

Example:

"dev-2c5e7cf2-9acf-4c8c-ab2f-b81f39d775a8"

timestamp
string
required

Response timestamp

Example:

"2025-11-12T20:49:03.293Z"