Error reference / rate-limited
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 workspace exceeded its fair-use rate limit. The response is HTTP 429 with a Retry-After header in seconds, and the X-RateLimit-* headers show the limit, what remains, and when the window resets. On the signing page the same slug covers the request-a-new-link throttle: the recipient asked recently and the sender was already notified.
What it means
The request was not processed. Limits are per workspace, shared by all its keys; GET /v1/me reports the sustained and burst figures under fair_use.
What to do next
Wait for Retry-After seconds, then retry. Spread bulk work over time and prefer webhooks to polling for status changes.
Problem body
Every error 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://docs.signenvoy.com/errors/rate-limited"
}