Check in a ticket
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.
bearerAuthAuthorizationBearer <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.
id*stringTicket id.
uuidChecked in.
application/json- response
data?curl -X POST 'https://hanghut.com/api/v1/tickets/497f6eca-6276-4993-bfeb-53cbbbba6f08/check-in'{ "data": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "status": "used", "checked_in_at": "2019-08-24T14:15:22Z" }}Cancel a subscription POST
**Not enabled.** Returns 503 until recurring billing is live (`SUBSCRIPTIONS_API_WRITE_ENABLED`). When enabled it dispatches `subscription.cancelled` — which is why that webhook event effectively never fires today.
Create a checkout POST
Returns a hosted `checkout_url` to send the buyer to. Inventory is held only until `expires_at`. For a reserved-seating event, pass `section_id` (from `GET /events/{id}/sections`); omitting it is a 400 rather than a general-admission fallback. The seats the buyer was given come back in `assigned_seats`.