Perigon · Deprecation

Perigon deprecation

Read from Perigon's own page on 2026-11-10. 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: 180 days
For a generally available API version, Perigon intends to provide at least 180 days of notice before a planned shutdown.
Read from Perigon's own page on 2026-11-10

Support window

Announcement channels

channel: changelog
We publish deprecations in the changelog and relevant API documentation.
Read from Perigon's own page on 2026-11-10
channel: email
Material notices may also be sent to account contacts.
Read from Perigon's own page on 2026-11-10

Deprecation / Sunset headers

deprecation: truesunset: true
During a deprecation period, affected responses may include the HTTP Deprecation header defined by RFC 9745.
Read from Perigon's own page on 2026-11-10

Versioning scheme

value: major version in URL path
Perigon places the major API version in the URL, such as /v1/ .
Read from Perigon's own page on 2026-11-10

Breaking change definition

A change that removes or renames a documented field, changes its meaning or type, makes an optional input required, or otherwise breaks a conforming integration requires a new major version unless it corrects a security or specification defect.
Read from Perigon's own page on 2026-11-10

Document

Download YAML · schema: API Commons Deprecation 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page