Tabfleet API versioning and deprecation

Current API and compatibility#

The public REST API uses /v1 paths at https://api.tabfleet.com. The OpenAPI document version describes the published specification and is distinct from the path version. Tabfleet is currently an alpha: clients should tolerate additive response fields, use documented request fields, and handle documented errors. No current /v1 endpoint has an announced deprecation or sunset date.

Compatible additions can remain within /v1. Planned incompatible migrations will be described here with affected operations and migration instructions. During the alpha, there is no guaranteed minimum notice period or service-level commitment. Urgent security, abuse-prevention, or upstream-provider changes may require immediate action.

Deprecation and sunset signals#

No API endpoints are currently deprecated or scheduled for removal.

API responses include the Link header below so clients can find this policy. The link does not mark an endpoint as deprecated.

Link: <https://tabfleet.com/docs/versioning>; rel="deprecation"

How future changes will be announced#

When an endpoint is deprecated, its responses will include a Deprecation header using the RFC 9745 date format: @ followed by Unix seconds.

If a removal date is scheduled, responses will also include a Sunset header using the HTTP-date format specified by RFC 8594. The removal date will be on or after the deprecation date.

These headers are omitted until dates are announced. A link to this policy alone does not announce a deadline.

Client migration guidance#

Review this page and the OpenAPI description when upgrading an integration. Keep OAuth resource identifiers exact, discover MCP tools through the authenticated client, and avoid assuming the OpenAPI version changes MCP protocol negotiation. For questions about an upcoming migration, contact jordan@daltonsolutions.com with the affected operation and client version, excluding credentials.