GatiFlow · Deprecation
GatiFlow deprecation
Read from GatiFlow's own page on 2026-11-09. 7 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: 90 days
An operation or a version is removed no sooner than 90 days after its deprecation is announced.Read from GatiFlow's own page on 2026-11-09
Support window
period: 90 days
A version receives fixes, security fixes included, until its Sunset date, and it is never sunset less than 90 days after its successor is published.Read from GatiFlow's own page on 2026-11-09
Announcement channels
channel: email
The notice goes by email to the owner of every organization holding an active API keyRead from GatiFlow's own page on 2026-11-09
Deprecation / Sunset headers
deprecation: truesunset: true
from the day of the notice its responses carry a Deprecation header (RFC 9745) and a Sunset header (RFC 8594) with the removal dateRead from GatiFlow's own page on 2026-11-09
Versioning scheme
value: URL path (/api/v1)
The version is in the path: every published operation lives under /api/v1.Read from GatiFlow's own page on 2026-11-09
Breaking change definition
A breaking change (removing or renaming an operation, a parameter or a field, or changing its type or meaning) ships only under a new version path, next to the current one.Read from GatiFlow'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