Presify API versioning and deprecation policy

What is versioned

The public machine surface is described in the OpenAPI document at https://presify.io/openapi.json. Its paths are permanent contracts: the MCP endpoint https://app.presify.io/api/mcp, the OAuth 2.0 endpoints under https://app.presify.io/api/oauth/, and the discovery documents under /.well-known/ never move and never change shape incompatibly. There is no version segment in any URL.

The MCP endpoint is versioned by the Model Context Protocol revision. Clients send the revision they speak in the MCP-Protocol-Version header (YYYY-MM-DD). The server currently serves 2026-07-28, 2025-06-18, 2025-03-26 and negotiates down to the newest revision at or below the one requested, so an older client keeps working when a newer revision ships.

What changes without notice

Additive changes ship as part of normal releases and are not announced ahead of time. Treat every response as open to new optional fields.

• New optional fields on any response, new operations, and new discovery documents.
• New MCP tools, prompts, and resources, and new optional arguments on existing tools.
• Support for a newer Model Context Protocol revision (older supported revisions keep being served).
• The tool list an individual connection sees can vary by plan and role at any time. That is the product working as designed, not a version change. Call tools/list rather than assuming the catalog.

How a retirement is announced

If an operation, a tool, a field, or a protocol revision is ever retired, we announce it at least 90 days before removal, in every place a client can see it:

• A Deprecation response header (RFC 9745) on every affected response, carrying the date the deprecation took effect, for example Deprecation: @1767225600.
• A Sunset response header (RFC 8594) on every affected response, carrying the date after which the operation stops working, as an HTTP date.
• A Link header with rel="deprecation" pointing at this page, where the replacement is described.
• The operation is marked deprecated: true in openapi.json, and a retired MCP tool is dropped from the server card and tools/list on the sunset date.
• An entry in the release notes shown in the app under What is new, and an email to the owners of every workspace with an active connection.

After the sunset date

A removed operation answers 410 Gone with the same JSON error shape the rest of the API uses (an error code, a message, and the replacement URL). A removed MCP tool disappears from tools/list, and calling it by name returns a tool result with isError and a message naming the replacement, so an assistant can adapt mid-conversation.

Credentials are never retired by a version change. OAuth grants, refresh tokens, and personal access tokens keep their published lifetimes.

Current status

Nothing is deprecated. As of release 26.9.4, no operation, tool, field, or protocol revision carries a Deprecation or Sunset header. This page and openapi.json are the machine-checkable places that will change first.