> 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.

# Status and incidents

> The Tillcast status page at status.tillcast.com: the services it shows, how availability is measured and what to do during an incident.

The status page is at [status.tillcast.com](https://status.tillcast.com). It is public and needs no sign-in. The dashboard links to it in its sidebar.

## What the status page shows

Each service has its current state and its availability. The page opens with the last 7 days by the hour, and can show the last 30 or 90 days by the day.

* **Printer connections.** Whether printers can reach Tillcast. If the data for it is missing or old, the state is unknown and not operational.
* **Printing.** Whether a job goes through the whole path and is printed.
* **Public API.** Whether the API accepts a job and answers when it is read.
* **Dashboard.** Whether the dashboard answers.

Webhooks are planned and do not exist yet; a webhooks service joins the page when they do. Current and past incidents are listed with their updates. A state is the worse of what the checks measure and what an open incident says. If the checks have stopped, the page says "Unknown, data stale" and still shows an incident that was declared by a person.

## How availability is measured

A canary sends a test job through the whole path every 5 minutes and confirms it as a real printer would. The job counts as printed when it was offered to the canary printer, downloaded and confirmed within 15 seconds, and the API then calls it `printed`. So the page shows whether printing works, not only whether a server answers.

The canary never declares an outage. Two failed checks in a row, about 10 minutes, set a service to degraded, and a person declares an incident. Announced maintenance counts as downtime.

## Where it runs

The status page runs apart from the service, in another EU region, so that it stays up when the service is down.

## What to do during an incident

* Check the status page first.
* When you ask for help, write to [contact@tillcast.com](mailto:contact@tillcast.com) and quote the `request_id` from the error. See [Errors](/api/errors).

See also [Security and data](/security#status-page).