The developer API

TQ has a REST API, so your own website, app or booking system can do what the dashboard does. Create a key under API Keys and send it with every request:

Authorization: Bearer tqk_your_key

What it can do

• Build your catalogue. Create events, shops, menus and donation pages, and add ticket types, products and dishes — prices, stock, options like size and colour, dates and venues. Edit, publish, unpublish and delete them too.
• Add pictures. Upload a photo to TQ, or give the address of one you already host and TQ fetches a copy. Either way TQ serves it, so your page can’t break because another server went down.
• Take payments. Start a mobile-money collection for one of your pages: the buyer approves a prompt on their phone, TQ collects, issues tickets or download links, and pays you out.
• QR codes and analytics. Create codes, re-point dynamic ones without reprinting, and read scan analytics.
• Hear about sales through a webhook, instead of asking us repeatedly.

Work from either side

Anything created through the API appears in your dashboard, and anything set up in the dashboard can be sold through the API. A page created through the API costs the same credits as creating it by hand. Things built around a file buyers pay for — downloads, audio and PDF flipbooks — are still set up in the dashboard.

Permissions

A key only gets what you tick when you create it. Two are deliberately separate: publications: write, because creating pages spends your credits, and orders: write, because it charges a buyer. A key keeps the permissions it was issued with, so to start creating pages with an older key, generate a new one.

What it costs

Each active key costs credits per month, charged on the 1st. If your balance can’t cover it the key pauses — nothing is deleted, and it works again as soon as you top up. We email you before that happens.

The full reference, with every endpoint, field and example, is under API Docs in your dashboard once you have a key.