# HakiChain API deprecation policy

This policy applies to the public HakiChain discovery API and any future public HTTP APIs published under `/api/v1`. Customer-data APIs follow separate enterprise agreements.

## Versioning

Public APIs are versioned in the URL path. The current public version is `/api/v1`. Breaking changes require a new major path version (for example, `/api/v2`).

## Deprecation and Sunset headers

When HakiChain deprecates a public API version or endpoint, responses include:

- `Deprecation: true` (or an HTTP-date) — RFC 8594 Deprecation header
- `Sunset: <HTTP-date>` — the earliest date the deprecated surface may be removed
- `Link: <https://hakichain.com/developers/deprecation-policy>; rel="deprecation-policy"`

HakiChain publishes at least **90 days** notice before removing a public version. A successor version remains available for at least 90 days after it is published.

## Non-breaking changes

Adding optional JSON fields, new endpoints, or additional response content types is not considered breaking. Clients should ignore unknown fields.

## Related resources

- [HakiChain developer portal](https://hakichain.com/developers)
- [HakiChain OpenAPI specification](https://hakichain.com/openapi.json)
- [Public discovery API](https://hakichain.com/api/v1/platform)