Skip to main content
Use a paid Business, Business+, or Platform site and a key with events:read and events:create. Create it under Account → Developers as described in authentication.

​
Verify your connection

Set TICKETSPOT_API_BASE to the production URL displayed in the endpoint playground and store your secret in TICKETSPOT_API_KEY.
A successful response includes success, events and pagination. Pass pagination.next_cursor as cursor to fetch the next page. A null cursor means the list is complete.

​
Create a draft event

A 201 response includes the event ID and created ticket IDs. Inspect warnings: an event can be created successfully while a downstream ticket operation fails. Add the missing ticket in the dashboard instead of retrying event creation. Events default to live when status is omitted. Retrieve the saved event using GET /events/{id} and confirm its schedule, venue and status in the dashboard before publishing it.

​
Find and scan an attendee

Search with GET /attendees/search?q=ann, optionally adding event_id to narrow the results. The search matches a case-insensitive prefix of a first name, last name, full name or email address and requires at least two characters. Send the chosen attendee ID and expected event ID to POST /scan. A 202 response means the check-in was accepted for processing. Ordinary ticket scans update through the existing task queue; query the attendee again shortly afterward to see the saved check-in status. A 409 means the scan was rejected. Read ticket_validity when present. The scanner enforces admission eligibility, required check-in answers, ticket validity and scan limits. Ordinary scans have a shared five-second duplicate guard. The optional idempotency_key applies to membership admission; it does not make ordinary ticket scans permanently idempotent. See Scan an attendee for the interactive request and rate limits and errors for retry behavior.