Build ticketing
into anything.

Syndicate what's on, no key required

Listing sites, aggregators and "what's on" apps can pull every public event on tickts straight from GET /api/v1/feed/events. One row per upcoming date, soonest first, wrapped in a { data, meta } envelope with meta.next for the following page. Poll with since= to receive only what changed, including cancellations as status: "cancelled" tombstones, so your copy never goes stale.

Unlisted events and draft events never appear. Private-location events expose the area only. Online events carry no physical location. All times are Europe/London ISO 8601; prices are in the organiser's currency (currency on each row: GBP or EUR). Rate-limited to 60 requests a minute; poll with since= rather than re-pulling everything.

The feed needs no key and never will. If you are syndicating tickts events on a schedule, ask us for a partner key anyway and send it as X-TK-Feed-Key (or Authorization: Bearer). It raises your rate limit above the anonymous 60 a minute, names you in our logs so we can warn you before anything changes, and registers your importer's address with our bot protection automatically, so a scheduled overnight pull from a datacentre never meets a challenge page. Email [email protected].

Pull the next page of music events

curl "https://tickts.co.uk/api/v1/feed/events?genre=music&per_page=200"

{
  "data": [{
    "id": "SE-kb759-20260912-2000",
    "event_id": 1041,
    "status": "scheduled",
    "title": "Hidden Jazz Club: Late Session",
    "description": "An intimate late-night set...",
    "url": "https://tickts.co.uk/events/hidden-jazz-club",
    "date_url": "https://tickts.co.uk/events/hidden-jazz-club?sub_event_id=SE-kb759-20260912-2000",
    "image": "https://tickts.co.uk/storage/events/card.jpg",
    "start_at": "2026-09-12T20:00:00+01:00",
    "doors_at": "2026-09-12T19:00:00+01:00",
    "timezone": "Europe/London",
    "venue": { "id": 812, "name": "The Bell Inn", "address": "12 High St", "city": "Bath",
               "postcode": "BA1 5AQ", "country": "GB", "lat": 51.38, "lng": -2.36 },
    "artists": [{ "name": "Ada Quartet", "headliner": true, "slug": "ada-quartet" }],
    "genres": [{ "name": "Jazz", "slug": "jazz", "parent": "Music" }],
    "category": "Music",
    "organiser": { "id": 812, "name": "Hidden Jazz Club" },
    "tickets": { "currency": "GBP", "sold_out": false, "cheapest": 12.5,
                 "types": [{ "name": "General Admission", "price": 12.5, "available": true }] },
    "sales_state": "on_sale",
    "updated_at": "2026-08-20T09:14:02+01:00"
  }],
  "meta": { "page": 1, "per_page": 200, "total": 1893, "total_pages": 10,
            "next": "https://tickts.co.uk/api/v1/feed/events?genre=music&per_page=200&page=2" }
}

Scoped keys, least privilege

Every key carries an explicit whitelist of scopes and grants nothing beyond them (a key with no scopes can do nothing — it fails closed). Send it as X-Api-Key or an Authorization: Bearer header.

Real-time, signed, retried

Subscribe an endpoint through the API and tickts pushes events to you the moment they happen — no polling. Every payload is signed with X-Tickts-Signature (HMAC-SHA256) so you can verify it's genuinely from us, and deliveries are queued and retried.

curl -X POST https://tickts.co.uk/api/v1/webhooks \
  -H "X-Api-Key: sk_live_your_key" \
  -d '{ "url": "https://you.com/hook",
       "events": ["order.created"] }'

Connect an AI assistant with MCP

tickts ships a Model Context Protocol server, so assistants like Claude and Cursor can operate your box office directly — check sales, issue comps, answer "how did Friday do?" — using your own scoped key. Your API is ready for the agentic web out of the box.

Endpoint: https://tickts.co.uk/api/mcp

Details that matter

Versioned (/api/v1), HTTPS-only, rate-limited with clear headers, consistent JSON errors, cursor pagination, and a machine-readable OpenAPI 3.0.3 spec you can generate a client from. Designed with developers (like us) in mind.