Skip to main content
POST
Mark an engager as read
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.
Mark one delivered engager as read after your integration has handled it. The response returns the engager with its read_at timestamp and webhook receipt, and the monitor’s unread_engager_count decreases. The request accepts an empty body or {}. A body that is present but not valid JSON returns 400.
The call is idempotent: marking an engager that is already read keeps its first read_at. Webhook retries use the engager ID as the event ID, so treat it as the durable acknowledgement key.
Marking an engager read does not delete it and spends no credits.

Next step

Review Create a post engagement monitor for webhook setup and signature verification.

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 engager after it was marked read.

engager
object
required