End of Life Policy

This page describes how Hunty manages the lifecycle of API versions, including deprecation notices and end-of-support timelines.

When a breaking change is introduced to an API, the version number in the URL path is incremented. For example, a breaking change to a v1 endpoint will result in a new v2 path:

/v1/endpoint  →  /v2/endpoint

Non-breaking changes (additive fields, new optional parameters) are deployed in-place without a version bump.

When a feature begins the deprecation process, it is added to the Active Deprecations table below with its communication date and expiry date.

All API Key holders are notified by email at the time of the deprecation announcement. The email includes:

• The feature or endpoint being deprecated
• The expiry date (2 months from the announcement)
• A link to the corresponding migration guide

Each deprecated feature remains supported for a maximum of 2 months from the date of the deprecation announcement. After the expiry date, the feature may be removed or disabled without further notice.

The table below lists all features currently under an active EOL process.

Migration guides are published as individual pages and linked from the Active Deprecations table above. Each guide describes what changed and how to update your integration before the expiry date.