Skip to main content
POST
Mark a job-change event as read
Job-change monitoring requires a V2 workspace API key. V1 (Bubble) API keys are not supported by these endpoints. Monitors and monitoring credits belong to the V2 workspace associated with the key.
Mark one event as read after your integration has handled it. The response returns the event with its read_at timestamp, and the monitor’s unread count decreases. The request accepts an empty body or {}. A body that is present but not valid JSON returns 400.
Treat the event ID as the durable acknowledgement key. Webhook retries use the same event ID, so processing it idempotently prevents duplicate downstream work.
An event can be marked read once. Marking an event that is already read returns 404 event_not_found, so treat that response as already acknowledged when you know the event exists. Reading an event does not delete it. You can still retrieve it through List job-change events or the monitor detail response.

Next step

Review Create a job-change 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
event_id
string<uuid>
required

Body

application/json

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

The body is of type object.

Response

The event after it was marked read.

event
object
required