Sudhanva API versioning and deprecation policy.

Current lifecycle status

API version /api/v1 is stable and is not deprecated. The major version is part of every canonical endpoint URL. Additive fields and new read-only resources may be introduced within v1; clients should ignore unknown response fields where practical.

Breaking changes

A change that removes or renames a field, changes its type or meaning, tightens accepted input, or otherwise breaks a conforming client will use a new major path such as /api/v2. Existing major versions will not silently change to an incompatible contract.

Deprecation and sunset signaling

Stable responses include an RFC 9745 Link relation pointing to this policy. A policy link does not mean v1 is deprecated. If a version is scheduled for retirement, affected responses will also carry a standards-compliant Deprecation Structured Field date and, when a shutdown date is known, an RFC 8594 Sunset HTTP-date.

Sudhanva will provide at least 90 days between the first public deprecation notice and sunset. The notice will appear here, in developer documentation, in llms.txt, and in the OpenAPI contract, with a migration path to the replacement version.

Client guidance

• Use only versioned /api/v1 URLs for new integrations.
• Inspect the Link, Deprecation, and Sunset response headers.
• Review the linked migration guide before the announced sunset date.