requestforms API versioning and deprecation policy
How RequestForms.io versions /api and /api/v1, and how it signals deprecation with RFC 9745 Deprecation and RFC 8594 Sunset headers.
RequestForms.io versions the public REST API in the URL path. Discovery routes such as health, stats, and the catalog live at /api. Paid organization list routes live at /api/v1. Breaking changes require a new major path such as /api/v2. Agents should pin to a versioned path and read this policy before they store a client.
This is the deprecation and sunset policy for the Request Forms API. Current paths are not deprecated. There is no scheduled sunset for /api/v1. When a path is deprecated, responses on that path include the RFC 9745 Deprecation header with the date deprecation began. When a removal date is set, responses also include the RFC 8594 Sunset header with that HTTP date. The old path stays until the Sunset date.
The OpenAPI document at /openapi.json lists every public operation. The JSON catalog at /api repeats those links and points back here. The requestforms CLI at /docs/cli and the MCP server at /mcp call the same versioned paths. Do not treat an unversioned guess as stable.
Questions about this policy go to [email protected]. The canonical HTML copy is https://requestforms.io/docs/deprecation. Machine-readable copies are /deprecation.md and this docs page with Accept: text/markdown.