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

# Suspension and pause

> How Tillcast stops printing for a location, a customer or an organization, and what happens to waiting jobs.

## Why suspension exists

A customer may stop paying, or a hotel may close for the season. An organization needs a way to stop printing for that customer or location without deleting anything.

## Three levels of suspension

| Level                  | Who does it                                                    | What happens                                                                                                                                    |
| ---------------------- | -------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| Location (pause)       | The organization, with `POST /v1/locations/{location}/suspend` | Every printer of the location is refused.                                                                                                       |
| Customer (suspend)     | The organization, with `POST /v1/customers/{customer}/suspend` | Every printer of the customer is refused.                                                                                                       |
| Organization (suspend) | Tillcast, for example when an organization stops paying        | The organization's keys can read and cannot write: a write is `403 organization_suspended`. People can still sign in to the dashboard and read. |

Both calls need the `customers:write` scope, and a key limited to one customer cannot suspend: a suspension is the organization's decision. `POST .../reactivate` on the same path undoes it. The dashboard has no screen for these yet.

A refused printer gets a bare HTTP `403` and prints nothing. Nothing needs to change on the printer. The printer object shows the status `customer_suspended` or `location_suspended`.

## New and waiting jobs during suspension

* Creating a job for a suspended customer or a paused location is refused with `409 customer_suspended` or `409 location_suspended`. A test print is refused the same way.
* Jobs that were already queued are kept until they expire. A payment may have been missed by accident, so Tillcast does not throw them away. If access returns before they expire, the printers print them. Otherwise they become `expired`. See [Jobs](/concepts/jobs).
* A job that the printer had already downloaded still finishes normally.
* A retry of a create that was accepted before the suspension is answered from the first request, with `200`. It is not turned into a `409`. See [Idempotency](/api/idempotency).

## Resuming after suspension

Resuming a location or a customer removes the refusal. Nothing changes on the printer. The design expects the printer to connect again by itself.

How a printer behaves while it is refused, and how long it needs to reconnect afterwards, has not been measured on a device yet. Expect a short delay, and check the printer's `last_seen_at` after you resume.