API Versioning and Deprecation Policy
Understand Manifest AI product versions, API versions, additive changes, breaking changes, and deprecation communication.
Manifest AI product releases and API versions are independent. V7 uses API v1; the API path changes only for an intentionally incompatible contract, not for every product release.
Compatible changes
Clients must tolerate documented additive evolution inside API v1.
- New optional response properties.
- New enum values where the schema declares extensibility.
- New endpoints and optional request fields.
- New webhook event types that a subscription did not request.
- Limit adjustments communicated through account data and response headers.
Breaking changes
Incompatible resource or behavior changes require a new major API path or an explicit migration window.
- Removing or renaming a documented field.
- Changing a field type or required meaning.
- Changing authentication semantics.
- Making a formerly optional field required without a migration window.
- Changing idempotency or charging behavior incompatibly.
Deprecation process
Deprecations are published before removal and include a replacement path.
Notices appear in this changelog and relevant documentation. Contract customers may receive additional operational communication under their agreement.