Rate limits and retries

Respect Retry-After and use backoff without duplicating submissions.

The public API applies layered limits:

  • 10 requests per minute per IP per form.
  • 60 requests per minute per IP across forms.
  • 120 requests per minute per form.
  • 600 requests per minute globally.
  • A separate preflight limit for CORS.

Malformed and spam attempts count toward rate limits.

429 response

HTTP/1.1 429 Too Many Requests
Retry-After: 42
Content-Type: application/json
{
  "success": false,
  "error": {
    "code": "rate_limited",
    "message": "Too many requests. Please try again later."
  },
  "request_id": "01JY8Z3K4M5N6P7Q8R9S0T1V2W"
}

Client guidance

  • Honour Retry-After seconds before retrying.
  • Disable the submit button while waiting.
  • Reuse the same idempotency key for the unchanged payload.
  • Add exponential backoff for 503 responses.
  • Do not retry 422, 403 or 409 without fixing the request.
  • Do not retry a used Turnstile token.
const retryAfter = Number(response.headers.get('Retry-After') ?? 5)
await new Promise(resolve => setTimeout(resolve, retryAfter * 1000))

503 responses

503 temporarily_unavailable means the form is not ready, Redis cannot safely apply limits, or Turnstile verification is unavailable. Retry later; do not bypass the check.