These endpoints give you each show's ticket sales, and let a ticket seller or box office system send its numbers straight into Confirmed. Sales you send show up in the show listing and on the show card, and they count towards tickets_available on the public Shows endpoint.

#How the numbers add up

A show's sales come in a breakdown, with one row per ticket type from each source. A source can be a ticket import set up in Data & API, or a feed you name yourself through this API. sold is the total across every row.

Each time a source sends its numbers, they replace that source's earlier rows and leave every other source's rows alone. You always send your full current totals, never the sales since your last call, so sending the same numbers twice doesn't count anything twice.

#GET /tickets

This endpoint returns the sales for every show in a date range that has sold any tickets.

curl "https://confirmed.show/api/v1/spectrum/tickets?ts_from=2026-07-01&ts_to=2026-07-31" \
  -H "Authorization: Bearer <token>"

[
  {
    "show_id": "nan3",
    "ts": "2026-07-21 21:00",
    "sold": 64,
    "updated_ts": "2026-07-19 14:05",
    "breakdown": [
      { "type": "Standard", "price": 15, "sold": 48, "source_type": "api", "source": "eventbrite", "api_key": "a1b2" },
      { "type": "Concession", "price": 10, "sold": 12, "source_type": "api", "source": "eventbrite", "api_key": "a1b2" },
      { "type": "Door", "price": 18, "sold": 4, "source_type": "red61", "source": null, "api_key": null }
    ]
  }
]

#Sales fields

#Sale fields

#GET /shows/{show_id}/tickets

This endpoint returns one show's sales, along with its history. If no show has that id, you get a 404.

curl https://confirmed.show/api/v1/spectrum/shows/nan3/tickets \
  -H "Authorization: Bearer <token>"

You get the sales fields above, plus history: the show's running total each time it changed, oldest first.

{
  "show_id": "nan3",
  "ts": "2026-07-21 21:00",
  "sold": 64,
  "updated_ts": "2026-07-19 14:05",
  "breakdown": [ ... ],
  "history": [
    { "ts": "2026-07-12 09:00", "sold": 20 },
    { "ts": "2026-07-19 14:05", "sold": 64 }
  ]
}

#PUT /shows/{show_id}/tickets

This endpoint sets one show's sales from one source. It needs a read-write key.

Each row in sales has type, sold, and optionally price, which defaults to 0.

curl -X PUT https://confirmed.show/api/v1/spectrum/shows/nan3/tickets \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
    "source": "eventbrite",
    "sales": [
      { "type": "Standard", "price": 15, "sold": 48 },
      { "type": "Concession", "price": 10, "sold": 12 }
    ]
  }'

You get the show's sales back, with every source included.

Give each feed its own source name. If you sell through two platforms, sending them as eventbrite and skiddle keeps both sets of numbers, where sending both under the same name would leave only the last one. To take a source's numbers off a show, send it with an empty sales list.

#PUT /tickets

This endpoint sets sales for several shows in one call, which suits a nightly sync. We check every show exists before writing anything, so if one id is wrong, nothing changes and you get a 404 naming it.

curl -X PUT https://confirmed.show/api/v1/spectrum/tickets \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{
    "updates": [
      { "show_id": "nan3", "source": "eventbrite", "sales": [ { "type": "Standard", "price": 15, "sold": 48 } ] },
      { "show_id": "p4rt", "source": "eventbrite", "sales": [ { "type": "Standard", "price": 15, "sold": 31 } ] }
    ]
  }'

You get the sales for those shows back as an array.

#Errors