Skip to main content
POST
Redeliver an engager webhook
Post engagement monitoring requires a V2 workspace API key. Legacy V1 API keys are not supported by these endpoints. Monitors and their credits belong to the V2 workspace associated with the key.
Re-arm one delivered engager’s webhook. Airscale resets the attempt count and sends the engager again to the monitor’s current webhook URL with its current signing secret. Redelivery never re-runs a check and spends no credits. A paused monitor holds the delivery until it is resumed. The request accepts an empty body or {}. The 202 response returns engager_id and the new webhook receipt, normally pending with attempt_count: 0. If a send for the engager is already in flight, its sending receipt is returned unchanged.
The engager keeps the same event ID and Idempotency-Key: post-engagement-engager:<engager_id> header. Your receiver may already have processed an uncertain delivery, so handle the engager idempotently.
A monitor without a webhook returns 422 webhook_not_configured. Track the outcome through the webhook receipt in List engagers.

Next step

Use Update a post engagement monitor to change the webhook URL or rotate its signing secret before redelivering.

Authorizations

Authorization
string
header
required

Use an Airscale workspace API key. Never expose the key in client-side code.

Path Parameters

monitor_id
string<uuid>
required
engager_id
string<uuid>
required

Body

application/json

Optional. Send no body or an empty JSON object ({}).

The body is of type object.

Response

The webhook delivery was queued again.

engager_id
string<uuid>
required
webhook
object
required