Check in a ticket

POST
/tickets/{id}/check-in

Admits the holder: sets status to used and stamps checked_in_at, then dispatches ticket.checked_in.

Note the vocabulary: the status becomes used, while the event and the timestamp field are named checked_in. There is no checked_in status value.

Not idempotent — a second call is a 409, which is what makes it usable as a turnstile.

Authorization

bearerAuth
headerAuthorizationBearer <token>

Authorization: Bearer hh_live_.... Create and revoke keys in Organizer → Settings → API. A key carries full access to its partner's data, including refunds and promo codes — treat it as a production credential and keep it server-side.

Path Parameters

id*string

Ticket id.

Formatuuid

Response Body

Checked in.

application/json
  1. response
data?
Example Request
curl -X POST 'https://hanghut.com/api/v1/tickets/497f6eca-6276-4993-bfeb-53cbbbba6f08/check-in'
Example Response
{  "data": {    "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",    "status": "used",    "checked_in_at": "2019-08-24T14:15:22Z"  }}