HangHut API
Ticketing, attendees and payouts. Every endpoint takes a Bearer API key from Organizer → Settings → API, and is limited to 100 requests a minute.
Reference
- List events — Events belonging to the authenticated partner, soonest first.
- Create an event — A venue event needs coordinates. Send `latitude` and `longitude`, or an `address` that geocodes — if geocoding is unavailable and no coordinates were sent, the request is rejected rather than stored without a location.
- Get an event
- Update an event — Partial update — send only the fields you are changing. Sending no recognised field is a 400 rather than a silent no-op. A successful update dispatches the `event.updated` webhook.
- List attendees — One row per ticket, including the buyer it belongs to.
- List seat-map sections — Sections for a reserved-seating event, with availability. Call this before `POST /checkouts` for a seated event: the checkout needs a `section_id`, and seats are assigned best-available inside it.
- Create a checkout — 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`.
- List orders
- Verify a ticket — The read behind a door scan — status, who holds it, and which tier.
- 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.
- Refund a ticket — Marks the ticket refunded and dispatches `ticket.refunded`.
- Sales aggregates
- List promo codes
- Create a promo code
- List subscription tiers
- List subscriptions
- Create a subscription — **Not enabled.** Returns 503 until recurring billing is live (`SUBSCRIPTIONS_API_WRITE_ENABLED`). The handler is written and validates its input, but no caller should depend on it yet. Read endpoints in this tag do work.
- Get a subscription
- Cancel a subscription — **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.
- List webhook endpoints
- Register a webhook endpoint — `url` must be HTTPS. `events` must be a non-empty array drawn from the enum — an unknown value is a 400 that names the offenders.