Amperity · Deprecation
Amperity deprecation
Read from Amperity's own page on 2026-11-09. 6 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.
Minimum notice
period: 6 months
At least 6 months notice will be given before any supported version is marked as unsupported.Read from Amperity's own page on 2026-11-09
Support window
period: 1 year
Each version of an endpoint will be supported for at least 1 year.Read from Amperity's own page on 2026-11-09
Announcement channels
channel: changelog
Monitor the changelog to know when new versions are available or when existing versions are updated or planned for deprecation.Read from Amperity's own page on 2026-11-09
Deprecation / Sunset headers
deprecation: truesunset: true
Deprecation and Sunset headers will be added at least 6 months before a deprecation.Read from Amperity's own page on 2026-11-09
Versioning scheme
value: date-based version identifiers (e.g. 2024-04-01) plus unstable and v0 for Streaming API
A version identifier is updated only when breaking changes occur.Read from Amperity's own page on 2026-11-09
Breaking change definition
A breaking change occurs when functionality within an API is modified in a way that causes integrations or applications to function abnormally or to stop working.Read from Amperity's own page on 2026-11-09
Document
Download YAML · schema: API Commons Deprecation 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page