Versioning and deprecation

The public API's operations stay under /api/v1. This page says how Wavo currently changes them, and how a caller is told.

What may change within v1Copy Anchor Link

• An answer may gain a field. The schemas in /openapi.json refuse no field they do not name, so a client built from them takes it.
• A read may gain an optional parameter, and the API a read or a problem code.
• A list's length and order follow the front page's.

What gets a new versionCopy Anchor Link

Wavo currently publishes a change that would break a caller — a field removed, renamed or given another type, a parameter made required, a read removed — under /api/v2, beside v1.

How a version is retiredCopy Anchor Link

1. From the day its successor is published, every answer of the retiring version carries Deprecation (RFC 9745), the date it was deprecated, and Sunset (RFC 8594), the date it stops answering.
2. It currently keeps answering at least 30 days after its first Deprecation header.

The public MCP serverCopy Anchor Link

Its tools are changed the same way: a tool or an optional input may be added, and a tool whose change would break a caller is currently published under a new name, the old one kept at least 30 days. The workspace's MCP server, open to Wavo's team today: any account can sign in, and every tool refuses one outside it, changes with the app.

Changes to this policyCopy Anchor Link

Wavo may give less notice, or none, for example where security, the law, abuse of the API or a source of its data requires it. It may change, limit or withdraw the public API, the public MCP server's tools or this policy at any time, by changing this page.