Skip to content

A ticket​

GET
/event-tickets/{code}

Whoever holds the code. Always the reservation's ticket layout (PartyTicket, kind: party, #2709). An order's party code answers the reservation. A legacy per-seat code answers the reservation too when it is the buyer's own seat or the reader is the buyer (its url carries the party code: the page moves there); any other seat (one a buyer sent a guest) answers that seat alone, with seat set and no party code, payment, receipt or actions. A request the hosts have not approved shows no code (code: null). Answers Referrer-Policy: no-referrer, never cached, never indexed.

Authorizations​

or
BearerAuth

In the browser, authentication rides on the httpOnly session cookies set by /cognito/signin or the Google / Apple sign-in at /cognito/oauth/{provider}. For scripts and for Swagger UI testing, paste an API key (fh_live_…, created with POST /api-keys); a Cognito JWT is accepted too. Sign-in does not return a token in its body.

Type
HTTP (bearer)

Parameters​

Path Parameters

code*

The ticket's code: 16 random bytes, base64url (22 characters). It is the ticket.

Type
string
Required
Pattern
"^[A-Za-z0-9_-]{22}$"

Responses​

The ticket.

application/json
JSON
"string"

Playground​

Server
Variables
Key
Value

Samples​

Powered by VitePress OpenAPI

Built with VitePress