Rate Limits

API requests are rate limited to keep the platform stable. The limits are the same on every plan. Each kind of request has its own limit, counted in a one-minute window. Most limits count per API key; the table shows the few that count per organisation or per form webhook.

Limits

When you go over a limit

The API returns 429 Too Many Requests with this body:

{
  "error": "rate_limited",
  "message": "Rate limit exceeded."
}

The 429 response carries these headers (form webhooks and /api/email/send answer 429 without them):

The MCP server answers a JSON-RPC error with code -32029 and HTTP status 429, with the same headers. Successful responses don't carry rate-limit headers.

Retrying

Wait until the reset time, or back off and retry:

async function fetchWithRetry(url: string, options: RequestInit, maxRetries = 3) {
  for (let attempt = 0; attempt <= maxRetries; attempt++) {
    const response = await fetch(url, options);
    if (response.status !== 429) return response;

    const reset = Number(response.headers.get('X-RateLimit-Reset'));
    const waitMs = reset ? Math.max(0, reset * 1000 - Date.now()) : Math.pow(2, attempt) * 1000;
    await new Promise((resolve) => setTimeout(resolve, waitMs));
  }
  throw new Error('Rate limit exceeded after retries');
}

Tips for staying within limits

• Batch writes — /api/crm/records/batch creates or updates many records in one request
• Cache responses — avoid re-fetching data that hasn't changed
• Use pagination — fetch records in pages rather than all at once

Next Steps

• Authentication — Set up API keys
• Records API — Query and manage records