> 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 dashboard has two test buttons

* **Test print** on a printer's page now queues the **short** test page: a few lines and a cut, to check the address, the printer and the paper.
* **Full test page** is a second button. It queues the long page (about 80 cm of paper) with every barcode type, QR code and image.
* The API is as it was: `POST /v1/printers/{printer}/test-print` queues the short page, and `?page=full` queues the long one. See [First connection](/printers/first-connection).

## Partners, retries and testing: new page and corrections

* **New page: [Provision a venue from your software](/provision-a-venue).** For a software vendor that sets printers up for its own customers: a customer, a location and a printer through the API, the key and scope of each step, your own ids, safe retries, what to do when the answer that holds the printer URL is lost, handing the URL to the venue, and the first test page.
* **SDKs.** Both packages call the live API unless you set `baseUrl` (TypeScript) or `base_url` (Python), without `/v1`. They retry an answer of `408`, `429` or `5xx` (Python also `409`) and wait for `Retry-After` inside the call, and they do not retry a timeout or a dropped connection: retry that yourself with the same `Idempotency-Key` and body. See [SDKs](/getting-started/sdks) and [Create a print job](/create-a-print-job#retry-safely). The READMEs of the packages say so from the next version.
* **Corrections.** A `text` block of spaces or of a no-break space is accepted and prints a blank-looking line, and a document with no block, or one that prints nothing (blocks of only blank lines, a `text` block of nothing, a `receiptline` of only white space), is `422 document_empty`. A `cut` or a `rule` alone is accepted. A replay of a create returns the object as it is now. A job that the printer has taken stays `delivered` after `expires_at` until the printer confirms it, a full queue finishes it as `expired`, or its bytes are gone (from an hour after `expires_at`) and the printer's request for it ends it `failed` with `payload_unavailable`: such a job with `delivered_at` set may have printed. A job that never ends is deleted from 7 days after `expires_at`. A job past `expires_at` does not count against the 50 waiting jobs. The full test page is about 80 cm. See [Idempotency](/api/idempotency), [Jobs](/concepts/jobs) and [Errors](/api/errors).
* **Testing.** There is no safe way to test against the live API today: no test mode, no virtual printers, no webhooks and no preview call over HTTP. [Build with an agent](/build-with-an-agent) says what an agent does instead, and has a brief for an agent that integrates Tillcast into a point of sale.
* **Update 2026-10-25.** Tillcast has no virtual printers for customers and no test mode.