> Tillcast is live: the API at https://api.tillcast.com/v1 and the dashboard at https://dashboard.tillcast.com. A key prints on real printers, so do not call the API unless asked. A job carries its receipt as "document", an array of blocks (the recommended way), or as "receiptline", ReceiptLine text, exactly one of the two: read https://docs.tillcast.com/create-a-print-job.md and https://docs.tillcast.com/concepts/documents.md before you write a job body. Do not code against what does not exist yet: webhooks, a template language, stored templates (a job has no template field), OAuth connections and connectors for Make, Zapier and n8n, and OAuth sign-in for the MCP server. SDKs for TypeScript (@tillcast/sdk, version 0.2.0 or later for blocks) and Python (tillcast) exist as pre-1.0 versions. To show a receipt in a web page without printing, there are the npm packages @tillcast/preview and @tillcast/html-render (0.x, no API key, no call to Tillcast to draw): read https://docs.tillcast.com/preview-a-receipt.md. The docs are the source of truth: check the index https://docs.tillcast.com/llms.txt and https://docs.tillcast.com/roadmap.md before you code against anything. For clean Markdown of any page, append .md to the page URL. The Tillcast MCP server is live at https://api.tillcast.com/mcp and takes an API key as a bearer token (setup: https://docs.tillcast.com/connect-an-ai-assistant.md). It acts on the live account and its tools print on real paper, so do not connect to it or call its tools unless the owner asked you to. The MCP server at https://docs.tillcast.com/_mcp/server is a different one: it only searches these docs and cannot call the Tillcast API.

## 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](/api/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`.