---
title: "Too Many Requests"
description: "Too many requests in a short time. Wait the number of seconds in the Retry-After header, then retry with backoff. See rate limiting for limits."
canonical: "https://signatureapi.com/docs/v1/errors/too-many-requests"
source: "https://signatureapi.com/docs/v1/errors/too-many-requests.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T11:41:57Z"
---

# Too Many Requests

Too many requests in a short time. Wait the number of seconds in the Retry-After header, then retry with backoff. See rate limiting for limits.

_Last verified against API version 1.18.0._

## What Happened

The client sent more requests than its rate limit allows. The API returns this error with a `429` status code when requests with an API key, requests from the [MCP server](https://signatureapi.com/docs/ai-toolkit/mcp/overview), or API requests made through the `signatureapi` CLI exceed their limits. For the limits, see [Rate limiting](https://signatureapi.com/docs/api/rate-limiting).

> **Tip:** The response includes a `detail` property with more information about this error.

## Example response

```json 429 Too Many Requests (application/problem+json)
{
  "type": "https://signatureapi.com/docs/v1/errors/too-many-requests",
  "title": "Too Many Requests",
  "status": 429,
  "detail": "Too many requests for this user. Retry after the number of seconds in the Retry-After header."
}
```

## How to Fix

- If the response includes a `Retry-After` header, wait that number of seconds before you retry. MCP and CLI responses always include it.
- Otherwise, wait before you retry, and double the wait after each `429` response. See [Handling rate limits](https://signatureapi.com/docs/api/rate-limiting#handling-rate-limits).
- Spread requests over time instead of sending them in bursts.
- If your API key needs higher limits, see [extended limits](https://signatureapi.com/docs/api/rate-limiting#extended-limits).

Still stuck? [Contact support](https://signatureapi.com/support).
