Documentation
Getting started

Rate Limits

Limits in place across api.live-direct-marketing.online. All values are enforced; the API returns 429 when a limit is exceeded.

POST /v1/signup

  • 5 signups per IP / hour (primary defense).
  • 50 signups globally / hour (anti-botnet ceiling — protects the queue when many IPs coordinate).
  • Edge burst smoothing at the proxy: 2 r/s with a burst of 10.
  • Body size cap: 64 KB — larger payloads return 413 Payload Too Large.

The IP-based and global counters reset on a sliding 1-hour window. The counter is incremented only after the email format passes basic validation, so malformed bodies (400) do not consume your budget.

Other /v1/* endpoints

  • Per-IP rate limit at the proxy: 2 r/s with a burst of 20.
  • Body size cap: 1 MB.

Delivery quota

Sandbox keys (issued by POST /v1/signup without full_account: true) get a monthly quota of 500 outbound messages. The remaining count is exposed via GET /v1/me in the quota object. The window rolls forward on the first day of every month (UTC).

Once the quota is exhausted, POST /v1/messages returns 402 Payment Required with error: "quota_exceeded". Contact welcome@live-direct-marketing.online to raise limits.

429 response shape

HTTP/1.1 429 Too Many Requests
Content-Type: application/json

{
  "error": "rate_limited",
  "message": "Too many signups from your address. Try again in an hour."
}

The proxy may also return a bare 429 with no JSON body when the edge burst budget is exhausted (e.g. many requests in the same second). In both cases, back off and retry after the window resets.