Deprecations

How a route leaves

1. Announced. The route keeps answering exactly as before for at least 30 days. Every response carries the Deprecation, Sunset and Link headers, and the reference marks the operation deprecated, with its sunset date and its replacement.
2. Sunset. From the sunset day, the route answers 410 Gone, with its replacement in the body.
3. Forgotten. After a year or more, the route answers 404 like any unknown address.

A version 1 route usually leaves under both of its spellings at once, the bare path and /v1/. A notice about version 1 never covers /v2/.

The headers

For example, a version 1 route that /v2/validators/{id}/ replaces sends these headers beside its usual body:

Deprecation: @1791763200
Sunset: Wed, 11 Nov 2026 00:00:00 GMT
Link: <https://api.taoswap.org/changelog/>; rel="deprecation"; type="text/html", </v2/validators/{id}/>; rel="successor-version"

• Deprecation (RFC 9745): when the deprecation was announced, as a UNIX timestamp after @, midnight UTC on that day.
• Sunset (RFC 8594): midnight UTC on the day the route stops answering. It answers through the day before.
• Link: rel="deprecation" points to the change log, and rel="successor-version" gives the replacement route as a path template, when there is one.

Watch for these headers in your client, for example by logging a warning whenever a response carries Deprecation.

After the sunset

The route answers 410 Gone with the API’s usual error envelope and the code ENDPOINT_REMOVED. Its detail gives the day it stopped (removed_on), its replacement, or null when nothing replaces it, and the reason. The three headers stay on that answer.

Fields

A field can leave a route the same way: the same notice period and the same announcements, but no header, since the route itself stays. The field keeps its value until the sunset, then leaves the response.

Where to follow announcements

• The change log, api.taoswap.org/changelog: every route and field on its way out, with the day it stops, the days left, its replacement and what to do, each entry with its own link.
• Its JSON twin, api.taoswap.org/changelog.json: the same entries for scripts, plus the policy itself (sunset_window_days, tombstone_keep_days).
• Its Atom feed, api.taoswap.org/changelog.atom: subscribe with a feed reader or a bot.
• Discord: each notice is posted in the #api-changelog channel of the Kusanagi Ventures Discord when it is announced, again 7 days before the sunset (and 30 days before, when the notice period is longer), and on the sunset day.

The change log lists only what is leaving. New routes and fields are not announced there.

If a sunset date is a problem for your integration, say so on Discord before it passes.

What changes without notice

• New routes, fields and filters appear without announcement. Your client should accept fields it doesn’t know.
• A wrong value is fixed in place, under the same field name.
• A change of shape gets a new version, such as /v2/, and the old version leaves through this process.