The monthly cap

The monthly cap is nearly used

80 percent of the monthly cap is used.

postWebhookcap_warning

Headers

Sendora-Signaturestring required

t= the Unix time of sending, then v1= an HMAC-SHA256 over <t>.<body> for each live secret of the webhook, the newest first. Verify one before you trust the body.

Sendora-Eventstring required

The event, the same as event in the body.

Sendora-Delivery-Idstring required

The delivery, the same as id in the body and on every retry of it.

User-Agentstring required

Sendora-Webhooks/1.

Payload

idstring required

The delivery's id. A delivery may arrive more than once, so key your handling on it.

attemptinteger required

The attempt number, from 1.

scope'account' | 'server' | 'test' required

Whose cap it is: account for the account's, server for a server's own, test for the cap the account's test servers share.

serverIdstring nullable required

The server whose cap it is; null for the account's or the test servers' cap.

capinteger required

Emails the scope may send in the month.

usedinteger required

Emails sent in the month so far.

periodStartstring date-time required

The month the counts are for: its first moment, in UTC.

periodEndstring date-time required

The first moment of the next month, in UTC.

occurredAtstring date-time required

When it happened.

event'cap_warning' required

Example payload

{
  "id": "4d6f8a0b-2c4e-4f6a-8b0c-2d4e6f8a0b1c",
  "attempt": 1,
  "scope": "account",
  "serverId": null,
  "cap": 50000,
  "periodStart": "2026-09-01T00:00:00.000Z",
  "periodEnd": "2026-10-01T00:00:00.000Z",
  "used": 40000,
  "occurredAt": "2026-09-24T09:30:00.000Z",
  "event": "cap_warning"
}

Response

Acknowledges the delivery. Any other answer, or none within 10 seconds, is retried.

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.