Letterby Docs

Rate limits

Request limits, the headers that report them and how to back off.

Requests are limited per key, per team and per IP address. The strictest limit applies.

LimitRequestsWindow
Per API key601 minute
Per team, across all its keys3001 minute
Per IP address, before the key is checked1201 minute

Headers

Authenticated responses report the limit closest to running out.

HeaderMeaning
X-RateLimit-LimitRequests allowed in the window.
X-RateLimit-RemainingRequests left in the window.
X-RateLimit-ResetWhen the window resets, in Unix seconds.

When you hit a limit

The API returns 429 with a Retry-After header in seconds.

{
  "error": {
    "type": "rate_limit_error",
    "code": "rate_limit_exceeded",
    "message": "Too many requests. Slow down and retry after the interval.",
    "request_id": "req_5f2c9a1e7b3d4c6f8a0b1c2d3e4f5a6b",
    "docs_url": "https://letterby.com/docs/api/errors#rate_limit_exceeded"
  }
}

Wait for Retry-After seconds, then retry. See Handle errors for code.

Stay under the limit

  • Use webhooks instead of polling for changes.
  • Request up to 100 items per page with limit.
  • Run bulk jobs one request at a time, not in parallel.

On this page