Skip to main content
POST
Check In E-Ticket
LatePoint Pro feature. E-Tickets require LatePoint Pro Features with E-Tickets enabled in LatePoint settings. Otherwise this endpoint returns 503 (feature_not_available or feature_disabled). See Pro features.
This endpoint runs the same validation as the LatePoint Pro ticket scanner, so you can use it to build your own door-check app.
  • A ticket can be checked in once per calendar day. On multi-day events the same ticket can be checked in again on each event day.
  • A group ticket checks in all remaining attendees of its registration.
  • When every attendee of a registration is checked in for the day, the registration status becomes checked_in.

Request Body Parameters

Send either code or ticket_id.
string
Ticket to check in. Accepts the raw ticket code, the ticket URL or the content of its QR code.
integer
ID of the ticket to check in
string
Day to check in for (YYYY-MM-DD). Defaults to today in the site timezone.

Example Request

Response

The response tells you whether the attendee may enter (admitted) and why (verdict). data is the ticket after the check-in.

Verdicts

A rejected ticket still returns HTTP 200 with admitted: false, except not_found.
The data object above is shortened; the actual response contains the full ticket.
The message text comes from LatePoint Pro and may vary with its version and the site language. Use verdict and admitted in your code.

Error Responses