Skip to navigation

The rule for API versions is written down

  • No breaking changes within a version date. From the day the page was published, a version date does not change in a way that breaks code written for it. A breaking change comes only with a new version date. See Versioning.
  • What counts. Removing or renaming a field, changing a type, a new required field or parameter, and a different status code or error code for a case that already has one are breaking. A new optional field, a new endpoint and new detail in an error are not.
  • Notice and old versions. A breaking change to the REST API /v1 takes effect no earlier than 6 months after Tillcast e-mails the owners of the organization, and a version date that a newer one has replaced stays available for at least 12 months. This is section 17 of the Terms of service. It covers only /v1: the MCP server is not covered, and a change of a limit or the enforcement of a rate limit keeps a notice of 30 days.
  • Why. The job body changed from an object to an array of blocks on 2026-10-16 under the same date. The page says so, and no longer says that the API can change under a date.
  • Unchanged. The API is as it was, and the current version is still 2026-10-01.