#Public APINo key

The public API gives you read-only JSON of the shows you've made public, and of the fields you've set up for each show type. It only shares information that isn't sensitive, with no fees, call times, contact details or bookings that aren't confirmed yet. Both endpoints accept GET, return JSON and allow cross-origin calls, so a few lines of fetch in a page is the whole integration. Their URLs are safe to put in a page anyone can view.

const shows = await (
    await fetch("https://confirmed.show/api/v1/your-production/shows.json")
).json();

You can point a tour page, a what's-on listing or a poster wall at it, or feed the shows into your site's build or CMS. The show type file is served from a CDN and answers in under 50ms.

• ShowsYour public shows as JSON: dates, venues, promotion and confirmed lineups.
• Show type metadataPublish your own fields against each show type, and read them back as a static JSON file.

#Private APIAPI key

The whole production: shows and the spots on them, ticket sales, venues and their rooms, acts, and your team. A read-only key reads all of it. A read-write key can also create and update shows, acts and venues, send in ticket sales and upload artwork. Requests go to https://confirmed.show/api/v1/<production>/, and you generate keys on your production's Data & API page.

Sync a ticketing system, pull your bookings into a spreadsheet or a dashboard, put a festival run in from a schedule you already have, or automate anything you'd otherwise do by hand in the app.

• Authentication and API tokensWhere to put your token, and how the server looks for it.
• Generate and manage API keysCreate, copy and delete keys from the Data & API page.
• ShowsRead, create and update shows, their spots and their promotion.
• Meta fieldsThe custom fields your production keeps on shows and show types, with their names and types.
• Ticket salesRead how many tickets each show has sold, and send in sales from your own ticket seller.
• Show typesYour show types, with the metadata you fill in for each.
• VenuesYour venues and the rooms inside them: read them, add new ones and keep their details up to date.
• ActsThe acts on your books: find them by name or tag, add new ones and keep their details up to date.
• TeamWho is on the production, and what they can do.
• File uploadGet a signed URL, send your file, keep the link.

#ShowtimeControl key

Drive a live show from outside Confirmed: move the running order on, call the break, and say which show is live. A control key reaches these two endpoints and nothing else, so you can leave one on a machine backstage without handing over your bookings.

Wire a button on the desk, fire the next cue from QLab or a stream deck, or start the night on a timer.

• Show controlDrive a live show from outside Confirmed: next, previous, break.
• Current showRead, set and clear the show Confirmed treats as live.

#Coding agents

If you build with a coding agent like Claude Code, Cursor or Codex, you can install our skills so it knows the Confirmed API before it writes any code. It will then use the right endpoints and fields for your production without having to read these pages first.

npx skills add rgb-monster/confirmed-skills

An agent without skills can read these docs as plain text, starting from confirmed.show/llms.txt, which links to every page in markdown.