> ## Documentation Index > Fetch the complete documentation index at: https://docs.tikk.chat/llms.txt > Use this file to discover all available pages before exploring further. # Bookings > Every booking has a lifecycle. Statuses, fields, payment states and how to read them. Every booking runs through a lifecycle from request to meeting, decline or cancel. The `status` field is the source of truth for where a booking sits at any moment. ## Booking statuses | Status | Meaning | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | `pending` | Request received. In **manual approval mode** the meeting is waiting on your approval. In standard mode, a booking briefly sits here before confirming. | | `accepted` | Confirmed. Both parties are committed to the time. | | `declined` | You declined the request. The booker is notified and the slot is freed. | | `cancelled` | Cancelled after it was accepted. Either party can trigger this. | Manual approval mode (every booking starts `pending` until you accept or decline) is **Pro only**. On the free tier, bookings go straight to `accepted`. ## Booking fields The booking object returned by the API contains the following fields: Unique ID for the booking. Use it to retrieve or reference the booking in API calls. Current state. One of `pending`, `accepted`, `declined` or `cancelled`. See [Booking statuses](#booking-statuses). When the request was submitted, as a UTC ISO 8601 timestamp (e.g. `2025-09-15T08:42:00Z`). When the meeting starts, as a UTC ISO 8601 timestamp (e.g. `2025-09-15T10:00:00Z`). `null` if not yet scheduled. Meeting length in minutes, as set on the service at booking time. Free-text description of what the booker wants to cover. URL-safe ID of the booked service (e.g. `discovery-call`). Last path segment of the booking URL. Human name of the service at booking time. `true` for group services (multiple attendees share the slot). Seat cap for group services. `null` if no cap or not a group service. `true` if this is a private personal invite not listed on your public page. Name and email of the person who made the booking. Additional attendees for group bookings, each with a name and email. Empty for one-to-one bookings. One of `video`, `in_person` or `none`. Human description of the location shown to both parties. Physical address for `in_person` meetings. Empty otherwise. Video call URL when location is `video`. `null` for in-person or none. One of `none`, `pending`, `paid`, `failed` or `refunded`. Free meetings always return `none`. Amount in **minor currency units** (e.g. `5000` is €50.00). See [Payment info](#payment-info). ISO 4217 code (e.g. `EUR`, `USD`). Reason given on decline or cancel. `null` while active. Any extra notes from you or the booker. ## Payment info Amounts are in **minor currency units**, the smallest denomination of the currency. For EUR and USD, divide by 100. ```text theme={null} amount: 5000, currency: "EUR" → €50.00 amount: 2500, currency: "USD" → $25.00 amount: 0, currency: "EUR" → free ``` Free services always return `payment.status = "none"` and `payment.amount = 0`. `pending` means the invoice is issued but not yet paid. For paid bookings that haven't been paid yet, the booking object also has a `meeting_link` field. That's the **checkout link** the booker uses to pay. It's not the same as `conference_link`, which is the video URL for the meeting itself. Don't present `meeting_link` as where the meeting happens. Fetch bookings via the API: * [List Bookings](/api-reference/bookings/list-bookings). Paginated list with status and date filters. * [Get Booking](/api-reference/bookings/get-booking). Full booking object for a single ID.