Integrations

Integrations

The Tillcast API works with any software that can send an HTTPS request. This page says what that means today, and what has been announced and is not built. A statement is marked Status: Today when it works now andStatus: Coming soon when it is planned. Coming soon means planned, with no date.

Template editor

Status: Coming soon A visual block editor for receipt templates, with loops, conditions and a live preview. You will be able to put it in your own app, so that your users can design their receipts.

In the editor you will place blocks one under another, repeat a block for every item of a list (a loop), show a block only when a condition holds, and watch the receipt change in a live preview. That preview already exists on its own as a package, @tillcast/preview: it draws a receipt in your page, in the browser, with no request to Tillcast.

It is designed to be embedded: a web component with a React wrapper, so it works in any framework and on a plain HTML page, and your page can drive it with its own buttons. Tillcast's own dashboard is planned to use the same editor, and the editor is planned to be released under the Apache License 2.0, as the preview package is.

Nothing of the editor is released, so there is nothing to try yet.

Any tool that sends an HTTP request

Status: Today For example Make (HTTP module), Zapier (Webhooks by Zapier) or n8n (HTTP Request node), with an API key. Documentation

Each of them sends an HTTP request. Tillcast has no connector for them yet, so you fill in the request yourself: a POST with your API key and the receipt as a list of blocks (text, tables, rows, rules, barcodes, QR codes and images). The documentation has the address, the fields and the errors. Create the key for the tool with only thejobs:write scope, which is what creating a job needs.

If you write code, the TypeScript and Python SDKs (@tillcast/sdk ,tillcast ; pre-1.0, so method names can still change) make the same call.

Status: Coming soon OAuth connections and ready-made connectors for Make, Zapier and n8n.

The OAuth connections and the connectors are planned, not built, and have no date. Make, Zapier and n8n are names of their owners. Tillcast is not affiliated with or endorsed by them.

AI agents (MCP)

Status: Today Connect an MCP client that can send an Authorization header, with a restricted API key. The agent can list your customers and printers, show a receipt before it prints, and print it. Set it up

MCP, the Model Context Protocol, is a way for an AI agent to use the tools that another service offers. Tillcast runs an MCP server at https://api.tillcast.com/mcp. You connect an MCP client that can send an Authorization header, and the API key is the bearer token: the same restricted key that the REST API takes, so the key decides what the agent can do. Make a key for the agent with only the scopes it needs, and limit it to one customer if you can.

The server gives the agent tools for your customers, locations, printers and jobs, and one that shows a receipt without printing it. A key is shown only the tools its scopes allow. A tool that prints, prints on real paper, so let a person agree to a receipt before it prints. The documentation has the setup for each client and says which of them were tried with Tillcast.

Status: Coming soon Sign-in with OAuth, for AI assistants that cannot send an API key, is planned.

Sign-in with OAuth is planned, not built, and has no date. Until it exists, an assistant that offers only OAuth sign-in cannot connect to the server.

An agent that can send HTTP requests can also use the REST API directly, with the same key.llms.txt is a short description of Tillcast for agents.

Names and logos belong to their owners (Claude, ChatGPT, MCP, Zapier, Make and n8n). They appear in example pictures and are named only to say which tool is meant, and do not mean that the owners support or endorse Tillcast.

What stays true

  • Receipts are not kept for later. A job's content is deleted once the job is printed, failed, cancelled or expired, as the Security page says. Nothing announced here changes that: to show a receipt later, your own system keeps the data it was printed from.
  • You format your numbers and dates. The data of a template will be text: your system sends amounts and dates as they should print, and a template places that text, repeats it or hides it.
  • The editor is for your own users. You will put it in your own application, and the people who use your application will design their receipts there.

Tell us what you need

If you need a connector for a particular tool, an SDK in another language or something in the editor, write to us and say which. It helps us decide what to build first.

E-mail us Contact page