1. Home
  2. Platform & Integrations
  3. Admin API - Chobble Tickets

Admin API

The admin API lets another program manage a Chobble Tickets site with an API key instead of a login. A script, spreadsheet or shop screen can list, create, change and remove listings, groups, holidays and listing options, and read a listing's attendees.

Full event management

The admin API gives you complete CRUD control over your events:

  • List events - fetch all your events with attendee counts
  • Get event - retrieve a single event with full details
  • Create event - set up new events with all options including capacity, pricing, dates, custom fields, and more
  • Update event - modify any event property, with automatic slug uniqueness checking
  • Delete event - safely remove events with a confirmation step (you must provide the event name to confirm)
  • Activate / deactivate - toggle events on and off without deleting them

Groups, holidays and listing attributes, such as sizes and their options, have the same list, read, create, update and delete calls.

Authentication

The admin API supports two authentication methods:

  • API keys - generate keys in the admin panel, then pass them as Bearer tokens. Keys are stored securely using HMAC hashing, so the raw key is never saved to the database.
  • Session cookies - if you're already logged in, the API accepts your session cookie with a CSRF token header.

API key authentication means you can integrate with CI/CD pipelines, cron jobs, or any system that can make HTTP requests, with no browser session needed.

An API keys page showing a key named Autumn programme with its creation date and a last-used date
Each key carries the name its owner gave it, and the list shows when it was created and when it was last used.

Every event option

The API exposes the same options as the admin panel: name, capacity, pricing (fixed or pay-what-you-want), descriptions, dates, locations, groups, contact field selection (email, phone, address), webhook URLs, daily event settings, registration deadlines, transferability, hidden events, and more.

You send JSON, you get JSON back. No form encoding or multipart uploads to worry about.

Attendees and attributes

The API can read a listing's attendees, so scripts and dashboards can pull the same attendee data you see in the admin panel. There is also an attributes resource, which covers listing options such as sizes.

Combined with the public API (which needs no authentication for read-only event listings), the webhooks system, and the embeddable widget, you can build exactly the integration you need.

Example

An owner makes a key called "Shopfront" on the API keys page and copies it straight away, because the site shows it only once. A script then sends GET /api/admin/listings with the header Authorization: Bearer followed by the key, and gets back every listing as JSON. The same key can POST a new listing, which goes on sale at once. The full list of calls is in the API documentation.

Limits

A key acts as the site's owner within the API, so anyone holding it can change what you sell. It cannot open the admin pages a person uses, including the page where keys are made, and the owner can withdraw it at any time. The rules for keys are published as test cases.