Rate limit exceeded
Too many requests in a short window.
| Problem type | /problems/rate-limited |
|---|---|
| HTTP status | 429 |
| Emitted by | Signing page, REST API (/v1) |
| Title values | Rate limit exceededYou already asked recently. The sender has been notified.You can request a new code shortly |
| Response headers | Retry-After |
| Trigger |
REST API (/v1):
fair-use rate limit (D12)
Signing page:
request-new-link throttle
|
What happened
The response is HTTP 429 with a Retry-After header in seconds. Gateway fair-use and device-flow rate-limit responses also carry X-RateLimit-* headers. The same slug covers the concurrent event-stream limit and signing-page OTP or request-a-new-link throttles; ceremony responses do not carry the gateway rate headers.
What it means
The request was refused. Gateway fair-use limits are per workspace, shared by all its keys; GET /v1/me reports the sustained and burst figures under fair_use. Device-flow throttles are keyed by client IP, and ceremony throttles apply to recipient verification or link requests.
What to do next
Wait for Retry-After seconds, then retry. Spread bulk work over time and prefer webhooks to polling for status changes. Reading one document too often has its own answer, polling-too-fast; Polling and webhooks covers both.
Problem body
Every error the API returns is an RFC 9457 problem document with media type
application/problem+json. The type member is the
stable identifier to switch on; docs_url is this page.
{
"type": "/problems/rate-limited",
"title": "You can request a new code shortly",
"status": 429,
"instance": "/v1/...",
"docs_url": "https://staging.signenvoy-docs-b4g.pages.dev/errors/rate-limited"
}