Wabery API deprecation and sunset policy

Wabery gives you explicit versions and deprecation headers. No silent breaking changes.

Canonical policy URL: https://wabery.com/docs/deprecation/

Versioning

URL major version: https://api.wabery.com/v1
Dated behavior pin: Wabery-Version (current 2026-06-18)
OpenAPI: https://api.wabery.com/v1/openapi.json

Every handled REST response echoes Wabery-Version. Current, non-deprecated responses also send RFC 9745 Deprecation: ?0. That boolean false means the served resource is not deprecated.

Deprecation policy

Wabery gives at least 180 days’ notice before retiring a supported public API version, except when an urgent security or legal requirement makes that period unsafe. When a version or operation is deprecated, responses include:

Deprecation: @<unix-timestamp> (RFC 9745) when deprecation begins
Sunset: <HTTP-date> (RFC 8594) with the planned removal date
Link: <https://wabery.com/docs/deprecation/>; rel="deprecation"

The OpenAPI document marks affected operations with deprecated: true. No public REST version is currently scheduled for sunset.

Sunset policy

Sunset follows RFC 8594. The Sunset header appears only when a removal date is scheduled. Until then, agents should treat /v1 as stable, pin Wabery-Version, and watch for Deprecation flipping from ?0 to a date.

curl -I https://api.wabery.com/v1/openapi.json
# Deprecation: ?0
# Link: <https://wabery.com/docs/deprecation/>; rel="deprecation"