The Bookings API lets authenticated users reserve seats for a screening, view their booking history, and cancel upcoming reservations. All booking endpoints require a valid Bearer token. The API validates seat availability in real time and prevents double-booking.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/raczkodavid/Tikera/llms.txt
Use this file to discover all available pages before exploring further.
All bookings endpoints require authentication. Include
Authorization: Bearer {token} on every request.GET /api/bookings
Returns all bookings belonging to the authenticated user, with nested movie and room details.GET /api/bookings/
Returns a single booking. Returns403 if the booking belongs to a different user.
POST /api/bookings
Creates a new booking. The API checks seat availability, validates seat positions against the room dimensions, and calculates the total price from the ticket types.ID of the screening to book. The screening must be in the future — past screenings return
422.Array of seat objects. Minimum 1 seat required.
Array of ticket type selections.
total_price = screening.base_price × ticket_type.price_multiplier × quantity (summed across all ticket types)
200 with the created booking object (status: "confirmed") including nested screening, movie, and room data.
DELETE /api/bookings/
Cancels a booking by deleting it. Returns403 if the booking belongs to a different user. Returns 422 if the screening has already started.
204 No Content on success.
Error reference
| Status | Meaning |
|---|---|
401 | Missing or invalid Bearer token |
403 | Booking belongs to a different user |
422 | Validation error — seat taken, past screening, invalid seat position, or invalid ticket type |
500 | Unexpected server error |