> ## 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.

# Versioning and Deprecation

> How the Dune API changes and how endpoints are retired

## Versioning

The API version is part of the URL path, such as `/api/v1/...`. Within a version we only make backward-compatible changes:

* new endpoints
* new optional request parameters
* new fields in responses
* new values in enums

Your client should ignore response fields and enum values it does not recognize. Breaking changes, such as removing a field or changing its type, go into a new version or a new endpoint.

## Deprecating an endpoint

When we retire an endpoint, we:

1. Announce it in the changelog and on the endpoint's docs page, and name the replacement.
2. Send the `Deprecation` and `Link` [response headers](https://docs.dune.com/api-reference/overview/response-headers.md) on the endpoint from that day.
3. Set a removal date at least **6 months** after the announcement, and send it in the `Sunset` header. Security fixes may need a shorter period, with at least **30 days'** notice.
4. Remove the endpoint after the sunset date.

Deprecated endpoints keep working until their sunset date. To find out early, watch for the `Deprecation` and `Sunset` headers in your client.

## Currently deprecated endpoints

| Endpoint | Replacement | Sunset |
| - | - | - |
| `/v1/table/*` | `/v1/uploads/*`, see the [migration guide](https://docs.dune.com/api-reference/tables/endpoint/migration.md) | November 23, 2026 |


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