Rate limits

Limits protect every company on the platform. They are generous; a well-behaved integration rarely meets them.

Request limits

The two limits apply independently: many keys behind one IP share the IP budget. Successful responses do not carry rate-limit headers; you only see the limit when you hit it.

When you hit one

HTTP/1.1 429 Too Many Requests
Retry-After: 60
X-RateLimit-Limit: 3000
X-RateLimit-Subject: user:apikey:0199c38d-7a8b-7c9d-98f9-142536475827
Content-Type: application/problem+json

{
  "type": "https://officehero.io/errors/rate-limited",
  "title": "Too many requests",
  "status": 429,
  "detail": "Too many requests — try again in 60 seconds",
  "retry_after_s": 60,
  "code": "rate_limited"
}

The replay limits answer differently: X-RateLimit-Bucket names the limit (integrations-replay-minute, integrations-replay-failed-minute or integrations-replay-failed-hour) instead of X-RateLimit-Subject, and Retry-After counts down to the end of that limit's window, so it can be anything up to 60 seconds (3,600 for the hourly limit).

Wait Retry-After seconds before the next request. A small helper that also backs off on 5xx:

async function withRetry(send, attempts = 5) {
  for (let i = 0; ; i++) {
    const res = await send();
    if (res.status !== 429 && res.status < 500) return res;
    if (i === attempts - 1) return res;
    const retryAfter = Number(res.headers.get('Retry-After'));
    const wait = Number.isFinite(retryAfter) && retryAfter > 0
      ? retryAfter * 1000
      : Math.min(30_000, 500 * 2 ** i) * (0.8 + Math.random() * 0.4);
    await new Promise((r) => setTimeout(r, wait));
  }
}

Other limits

Need more? Tell support what you are building.