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

# Deprecation policy

> How Etherfuse announces, deprecates, and retires API behavior, and how much notice you get.

This page explains how the Etherfuse API changes over time and what you can rely on. Breaking
changes and deprecations are also announced in the [changelog](/changelog), tagged `Breaking` or
`Deprecated`.

## Lifecycle

Every endpoint, field, or flow moves through four stages:

| Stage          | What it means                                                                                              |
| -------------- | ---------------------------------------------------------------------------------------------------------- |
| **Active**     | Fully supported. Safe to build on.                                                                         |
| **Deprecated** | Still works, but scheduled for removal. Announced in the changelog with a migration path. Start migrating. |
| **Sunset**     | A fixed end date is set. The behavior still works until that date.                                         |
| **Removed**    | No longer available after the sunset date.                                                                 |

## Breaking vs. non-breaking changes

What counts as **non-breaking** (no migration required):

* New endpoints, resources, or optional request parameters.
* New fields in a response or webhook payload.
* New webhook event types or enum values.

What counts as **breaking** (we provide a migration path):

* Removing or renaming an endpoint or field.
* Changing the type or meaning of an existing field.
* Changing an authentication flow.

## How we announce changes

When a breaking change or deprecation is scheduled, we use the loudest path available, because this
is money infrastructure:

1. A [changelog](/changelog) entry tagged `Breaking` or `Deprecated`, with migration steps.
2. A direct email to API-key holders.
3. An in-dashboard banner for breaking changes.
4. The affected endpoint is marked deprecated in the [API reference](/api-reference/introduction).

## Current deprecations

*No active deprecations.*

<Note>
  When something is scheduled for deprecation, it appears here with its deprecation date, sunset date,
  and a link to the migration guide.
</Note>