Skip to main content
POST
Scan an attendee

Authorizations

Authorization
string
header
required

ts-{uuid}-{secret}. Every key requires its independent secret.

Body

application/json
attendee_id
string
required
Example:

"attendee-uuid"

event_id
string

Optional expected event ID. The attendee must belong to this event.

idempotency_key
string

Stable request ID for membership admissions. Ordinary ticket scans use a shared five-second duplicate guard and do not provide long-term idempotency.

Pattern: ^[A-Za-z0-9_-]{16,128}$

Response

Scan accepted.

success
boolean
accepted
boolean
attendee
object
ticket_validity
object