> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dune.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Response Headers

> Rate limit and deprecation headers returned by the Dune API

The Dune API uses standard HTTP headers to tell clients about their rate limits and about endpoints that are being retired. Browser clients can read all of these headers.

## Rate limit headers

Responses to authenticated requests include the [rate limits](https://docs.dune.com/api-reference/overview/rate-limits.md) that applied to the request. The headers follow the IETF [RateLimit header fields draft](https://datatracker.ietf.org/doc/draft-ietf-httpapi-ratelimit-headers/).

| Header | Format | Meaning |
| - | - | - |
| `RateLimit-Policy` | `"<policy>";q=<quota>;w=<window>` | The limit that applies: `q` requests per window of `w` seconds. |
| `RateLimit` | `"<policy>";r=<remaining>;t=<reset>` | `r` requests left in the current window, which resets in `t` seconds. |
| `Retry-After` | `<seconds>` | Sent only with `429 Too Many Requests`. Wait at least this many seconds before retrying. |

A request can be subject to more than one policy. Each policy appears as a separate entry in the list, and the most restrictive one applies.

| Policy | Applies to |
| - | - |
| `ip` | Every request from your IP address |
| `write` | [Low limit endpoints](https://docs.dune.com/api-reference/overview/rate-limits.md) (write-heavy operations) |
| `read` | [High limit endpoints](https://docs.dune.com/api-reference/overview/rate-limits.md) (read-heavy operations) |
| `default` | The Dune MCP server |

For example, a read request on the Plus plan that hit its limit returns:

```http theme={null}
HTTP/1.1 429 Too Many Requests
RateLimit-Policy: "ip";q=1000;w=1, "read";q=200;w=60
RateLimit: "ip";r=999;t=1, "read";r=0;t=37
Retry-After: 37
```

> [!NOTE]
>
> A positive `r` does not guarantee that the next request will be accepted. If the headers are missing, for example on a `401 Unauthorized` response, back off exponentially before retrying.

## Deprecation headers

Endpoints that are being retired send these headers on every response. See the [versioning and deprecation policy](https://docs.dune.com/api-reference/overview/versioning.md).

| Header | Format | Meaning |
| - | - | - |
| `Deprecation` | `@<unix timestamp>` | When the endpoint was or will be deprecated ([RFC 9745](https://www.rfc-editor.org/rfc/rfc9745)). |
| `Sunset` | HTTP date, such as `Mon, 23 Nov 2026 00:00:00 GMT` | When the endpoint stops working ([RFC 8594](https://www.rfc-editor.org/rfc/rfc8594)). Sent once a removal date is set. |
| `Link` | `<url>; rel="deprecation"` | The page that explains the deprecation and names the replacement. |

Log or alert on these headers in your client so you notice a deprecation before the endpoint is removed.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.