delivery.status_changed

Event type: delivery.status_changed.

When it fires

A campaign, ad set or ad changed delivery status. Checked every 15 minutes.

Envelope

Every event shares these top-level fields. The event-specific fields are under data.

Field	Type	Required	Description
`id`	`string`	Yes	Unique event id. Deliveries are at-least-once, so dedupe on it.
`type`	`"delivery.status_changed"`	Yes
`createdAt`	`string (date-time)`	Yes
`apiVersion`	`"v1"`	Yes
`organizationId`	`integer`	Yes
`brandId`	`integer \| null`	Yes
`accountId`	`string \| null`	Yes	The ad account the event concerns.
`provider`	`string \| null`	Yes	The ad platform the event happened on. One of `meta`, `whop`.

Data

Field	Type	Required	Description
`data.level`	`string`	Yes	One of `campaign`, `adset`, `ad`.
`data.entity`	`object`	Yes
`data.entity.providerId`	`string`	Yes
`data.entity.koastId`	`string \| null`	Yes
`data.entity.name`	`string \| null`	Yes
`data.entity.campaignLaunchId`	`string \| null`	Yes
`data.from`	`string \| null`	Yes	The status Koast last recorded. Null when none was recorded yet. One of `LIVE`, `OFF`, `UNDER_REVIEW`, `REJECTED`, `SCHEDULED`, `PROCESSING`, `NOT_DELIVERING`, `DRAFT`.
`data.to`	`string`	Yes	Delivery status as Koast displays it. One of `LIVE`, `OFF`, `UNDER_REVIEW`, `REJECTED`, `SCHEDULED`, `PROCESSING`, `NOT_DELIVERING`, `DRAFT`.
`data.providerStatus`	`string \| null`	Yes	The ad platform's own status string, unmapped.
`data.changedAt`	`string (date-time)`	Yes

Example payload

{
  "id": "evt_2xKq7Vb9mN4pR8sT",
  "type": "delivery.status_changed",
  "createdAt": "2026-09-19T14:30:00Z",
  "apiVersion": "v1",
  "organizationId": 1,
  "brandId": 1,
  "accountId": "string",
  "provider": "meta",
  "data": {
    "level": "campaign",
    "entity": {
      "providerId": "string",
      "koastId": "string",
      "name": "string",
      "campaignLaunchId": "string"
    },
    "from": "LIVE",
    "to": "LIVE",
    "providerStatus": "string",
    "changedAt": "2026-09-19T14:30:00Z"
  }
}

Delivery headers

Header	Required	Description
`webhook-id`	Yes	The delivery id; identical across retries of the same event. Dedupe on the envelope `id`.
`webhook-timestamp`	Yes	Unix seconds at signing time. Reject deliveries older than 5 minutes.
`webhook-signature`	Yes	Space-separated `v1,<base64 HMAC-SHA256>` signatures (Standard Webhooks). Two are sent while a rotated secret overlaps.

Acknowledge

Your response	Meaning
`2XX`	Return any 2xx status to acknowledge the delivery.

Signing, retries and endpoint setup are in the Webhooks guide.