Skip to Content

Rate limits

Requests per minute per key, set by your plan, with the standard RateLimit headers on every response.

Secret-key requests are limited per key, per minute, by your plan:

PlanRequests per minute, per key
Free60
Starter300
Pro600

See plans and limits for the full table. Each key has its own budget, so a nightly sync on one key cannot starve your check-in app on another.

Headers

Rate-limited responses carry:

HeaderMeaning
RateLimit-LimitRequests allowed in the current window.
RateLimit-RemainingRequests left in it.
RateLimit-ResetSeconds until the window resets.
Retry-AfterOn a 429 only: seconds to wait before trying again.

Over the limit, you get 429 with the code rate_limited:

{
  "type": "https://whocoming.com/docs/errors#rate_limited",
  "title": "Too many requests",
  "status": 429,
  "code": "rate_limited",
  "detail": "Too many requests. Try again in 12 seconds.",
  "request_id": "req_..."
}

Wait Retry-After seconds and retry. A refused request does not use up any of your budget. The SDK does this for you.

Public endpoints

The public surface is limited per visitor's IP address, not per key:

  • RSVPs (POST /v1/public/events/{id}/rsvps): 5 a minute and 30 an hour, per IP address, per event.
  • Sandboxes (POST /v1/sandbox): a few per IP address per hour; over it answers 429 sandbox_limit.

IP addresses are hashed before they are counted.

On this page