Skip to main content
FinanceGPT Developer Platform

API compatibility & versioning

A public, machine-readable policy for stable, beta and experimental API lifecycle, contract pinning, deprecation and major-version boundaries.

Policy JSONCI delivery
Overview Quickstart API reference Guides LQM Builder SDKs Auth & webhooks Changes Versioning CI Support Certification Programme Ecosystem Solutions References Evidence exchange Status Marketplace API plans
API major
v2
Current public contract
Operations
349
228f3cf999f8…
Deprecated
0
Published lifecycle evidence
Scope mismatches
0
Must be zero for readiness

Compatibility classes

Compatibility commitments are explicit and tied to the persisted Developer Catalog and current OpenAPI fingerprint.
Stable

Existing documented request and response contracts are treated as compatibility commitments within the current major API version unless a published deprecation and sunset lifecycle says otherwise.

Beta

Beta operations may evolve before stable designation. Published lifecycle metadata remains the source of truth for deprecation and sunset state.

Experimental

Experimental operations are evaluation surfaces and do not carry the same compatibility commitment as stable operations.

Contract lock

Pin the current OpenAPI SHA-256 in CI and fail closed when the contract changes unexpectedly.
Contract lock JSON
228f3cf999f801d03634f0dad1fc6d296671bc13a8cf0d80994b00a57b62f910

Current FinanceGPT API v2 OpenAPI index SHA-256.

Deprecation and history boundary

Open change ledger

Deprecation and sunset status comes from persisted published Developer Catalog lifecycle metadata. FinanceGPT does not synthesize historical OpenAPI diffs that were never persisted.

Breaking-change rule: Breaking changes require an explicit lifecycle transition in the persisted Developer Catalog and a new major-version boundary before incompatible production replacement.

Authority boundary

Version policy and contract metadata do not grant API scopes, enable production access, promote LQMs, rebind QLMs, change billing, or create Financial Actions authority.