Scan Ticket
Scan a ticket using a scanner registered to your organization. If scanner_id is omitted, the first active scanner in your organization is used. The scanner’s profile rules, timeslot restrictions, and scan windows are enforced automatically. Requires the tickets.write scope.
Authorizations
Pass as Authorization: Bearer {token}. Accepts either an OAuth2 JWT access token or an API key (tk_live_...) created from the Tickable dashboard.
Path Parameters
Ticket ID
"c3d4e5f6-7890-4a1b-2c3d-4e5f6a7b8c9d"
Body
Scanner ID. If omitted, the first active scanner in your organization is used.
"e5f6a7b8-9012-4c3d-4e5f-6a7b8c9d0e1f"
Response
Scan result
"c3d4e5f6-7890-4a1b-2c3d-4e5f6a7b8c9d"
valid, scanned, cancelled, not_allowed "valid"
false
"Jane Doe"
"jane@example.com"
"A12"
"2026-06-15T14:30:00Z"
null
Other tickets in the same order, if the event has order scanning enabled