API Stability

Every public operation is marked stable or preview in the operation catalog, OpenAPI document, and endpoint reference.

Stable operations

Stable operations preserve documented request and response contracts within the current API version. Additive fields can appear, so clients should ignore unknown response fields. Incompatible changes require a versioned endpoint or a documented deprecation and migration window.

Preview operations

Preview operations have published API contracts, but preview status does not guarantee that an operation can start at a given moment. All 19 provider operations in All tools are open to guests, free accounts and paid accounts, subject to service health, credits, free-use limits, location and your access. Connected-account Mail and Drive operations need a signed-in account and are not part of the free tools. When a preview operation is opened, its request, result, pricing, or availability contract can change before promotion to stable. Changes are recorded in the API changelog. Preview does not mean that returned data is simulated.

Sources of truth

The generated OpenAPI document is the machine-readable contract. Endpoint reference pages explain billing, lifecycle, retention, retry, and safety behavior. Automated checks keep public routes, catalog metadata, examples, schemas, docs links, errors, scopes, and assistant guidance in sync.

Deprecation and sunset

When a stable contract must be retired, Chab documents the replacement, deprecation date, and sunset date in the changelog and relevant endpoint page. During the announced window the old contract remains available unless an urgent security or legal requirement makes that impossible. Preview changes do not receive the same compatibility window, but they are still recorded in the changelog.