Webhook events

spend.day_closed

An ad account's day ended, in its own timezone, with that day's spend.

Event type: spend.day_closed.

When it fires

An ad account's day ended, in its own timezone, with that day's spend.

Envelope

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

FieldTypeRequiredDescription
idstringYesUnique event id. Deliveries are at-least-once, so dedupe on it.
type"spend.day_closed"Yes
createdAtstring (date-time)Yes
apiVersion"v1"Yes
organizationIdintegerYes
brandIdinteger | nullYes
accountIdstring | nullYesThe ad account the event concerns.
providerstring | nullYesThe ad platform the event happened on. One of meta, whop.

Data

FieldTypeRequiredDescription
data.accountIdstringYes
data.datestring (date)YesThe closed day, in the ad account timezone.
data.timezonestringYesIANA timezone of the ad account.
data.spendnumber | nullYesTotal spend for the day. Null when it could not be read, never 0.
data.currencystring | nullYes

Example payload

{
  "id": "evt_2xKq7Vb9mN4pR8sT",
  "type": "spend.day_closed",
  "createdAt": "2026-09-19T14:30:00Z",
  "apiVersion": "v1",
  "organizationId": 1,
  "brandId": 1,
  "accountId": "string",
  "provider": "meta",
  "data": {
    "accountId": "string",
    "date": "2026-09-19",
    "timezone": "string",
    "spend": 12.5,
    "currency": "string"
  }
}

Delivery headers

HeaderRequiredDescription
webhook-idYesThe delivery id; identical across retries of the same event. Dedupe on the envelope id.
webhook-timestampYesUnix seconds at signing time. Reject deliveries older than 5 minutes.
webhook-signatureYesSpace-separated v1,<base64 HMAC-SHA256> signatures (Standard Webhooks). Two are sent while a rotated secret overlaps.

Acknowledge

Your responseMeaning
2XXReturn any 2xx status to acknowledge the delivery.

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

On this page