Thumble API lifecycle policy

API versioning and deprecation

The stable REST major version is /v1. Backward-compatible fields may be added; clients should tolerate unknown response fields and documented optional values. Breaking contract changes use a new major version. Before removing a documented stable operation, we will give at least 90 days’ notice in developer documentation and return Deprecation and Sunset headers on affected operations, with a Link to migration guidance. No documented v1 operation is currently deprecated or scheduled for removal. Read the API lifecycle policy.

Scope

This policy applies to operations published in the Thumble read API contract. Native device management and experimental disabled generation interfaces are not part of that stable read contract. Authentication stays required for account data. New scopes always require an explicit consent flow.

Recovering from changes

Read response headers before retiring an integration. A Deprecation header signals that migration is recommended; Sunset announces the removal date. Follow the linked migration documentation and test against the free synthetic sandbox. No v1 endpoint is currently scheduled for removal. Questions go to Thumble support.