API Deprecation Policy
Effective July 2026. This policy applies to all 1Claw public APIs including the Vault API, MCP server, and SDK.
Versioning
The 1Claw API uses URL-based versioning. The current version is v1. All endpoints are prefixed with /v1/. When a new major version is introduced, the previous version will remain available for at least 12 months.
Breaking changes
We consider the following to be breaking changes:
- Removing an endpoint or HTTP method
- Removing or renaming a required request field
- Removing a response field
- Changing the type of an existing field
- Adding a new required field to an existing endpoint
- Changing the authentication scheme for an endpoint
Non-breaking changes (adding optional fields, new endpoints, new enum values) may be introduced at any time without a version bump.
Deprecation process
- Announcement — Deprecations are announced at least 90 days before removal via the blog, changelog, and email to affected organizations.
- Sunset header — Deprecated endpoints return a
SunsetHTTP header (RFC 8594) with the planned removal date and aDeprecationheader with the deprecation start date. - Migration guide — A migration guide is published in the documentation before the deprecation period begins.
- Removal — After the sunset date, the deprecated endpoint returns
410 Gone.
Current deprecations
| Field / Endpoint | Replacement | Sunset |
|---|---|---|
| tx_max_value_eth | tx_max_value | 2026-12-31 |
| tx_daily_limit_eth | tx_daily_limit | 2026-12-31 |
| tx_spent_today_eth | tx_spent_today | 2026-12-31 |
SDK and CLI versioning
The SDK (@1claw/sdk) and CLI (@1claw/cli) follow semantic versioning. Minor version bumps may add new methods and types. Major version bumps indicate breaking changes with migration notes in the changelog.
Questions? Contact ops@1claw.xyz.