Autodisc API versioning and deprecation policy

Autodisc public REST endpoints use a major version in the URL, such as https://api.autodisc.xyz/api/v1/drops. Clients may depend on documented request fields, response fields, status semantics, and authentication rules for the lifetime of that major version.

Compatible changes

Autodisc may add optional request fields, response fields, enum values where the documentation marks the set as extensible, new endpoints, and new optional HTTP headers without changing the major version. Clients should ignore unknown response fields and must not infer that an undocumented enum set is closed.

A change that removes or renames a documented field, changes its type or meaning, makes an optional input required, removes an operation, or changes its authentication boundary requires a new major version unless it is necessary to resolve an active security or legal issue.

Deprecation signals

Autodisc announces a scheduled endpoint retirement in documentation and on the affected HTTP responses. A deprecated response includes:

Deprecation: @1782864000
Sunset: Thu, 31 Dec 2026 00:00:00 GMT
Link: <https://autodisc.xyz/docs/api-deprecation-policy>; rel="deprecation"; type="text/html"

Deprecation is an HTTP Structured Field Date as defined by RFC 9745. Sunset is an HTTP-date as defined by RFC 8594. The Link target identifies the migration guidance or current policy. These headers appear only on a deprecated operation; their absence means no retirement has been scheduled.

Notice and retirement

Autodisc provides at least 90 days between the published deprecation date and the sunset date for a stable public API operation. When practical, a compatible replacement is available before the notice period begins. Urgent security, abuse-prevention, legal, or data-integrity changes may use a shorter period; the reason and migration path will be published with the notice.

After the sunset date, a retired resource returns 410 Gone when preserving a distinct retirement response is practical. Clients must not treat a 404 or 410 as a transient retry condition. A 429 Too Many Requests is not a deprecation signal; follow Retry-After and the RateLimit response fields instead.

Client responsibilities

• Use documented versioned URLs rather than deriving internal routes.
• Log response status, request ID, and deprecation headers without logging authorization values or user secrets.
• Monitor Deprecation, Sunset, and Link headers during normal requests.
• Complete migrations before the advertised sunset date.
• Contact Autodisc support if published migration guidance is incomplete.