Skip to main content
Platform API Docs

Environments and Versioning

Keep sandbox, beta, and production bindings isolated while following immutable contract versions.

Version Public contract v1 Generated references follow approved public contract hashes Reviewed Jul 26, 2026 Next review Oct 26, 2026

The free Developer workspace is for non-production building and learning under published limits. External API or MCP client credentials use a separate scoped request and approval process.

Owner: Batoi Developer Experience Reviewed by: Batoi Platform Security Source revision: upgrade-jul-26-2026

Browse Batoi Platform API Documentation Environments and Versioning

Environments and Versioning

Environments

  • Sandbox is the default integration and verification environment.
  • Beta is an optional controlled promotion stage.
  • Production requires an independently approved binding and publication.

A binding is valid for one environment. Changing the envelope does not promote a credential.

Contract versions

Each publication points to one immutable contract version and SHA-256 contract hash. A new operation or schema requires a new compiled version, review, approval, and publication.

Runtime verifies that the operation UID, schema hash, method, scope, target binding, action class, and approval policy match the active contract. Documentation downloads are rebuilt from that same verified source.

Rollback

Publishers may roll back to an eligible prior approved version. Clients should use operation keys and schemas from the active reference and must not infer unpublished fields.

Compatibility

The configured www host is a compatibility address for the canonical apex endpoint, not a separate API product. Semantic behavior and authorization must remain equal.