GET /bookings/{id}. Retrieve a single booking by ID

The /bookings/{id} endpoint retrieves a single booking in full detail by its integer id. Use it to look up a record after a webhook, resolve a booking linked in another system or refresh stale data. The response is the same full Booking object as the list endpoint. There’s no abbreviated version.

Endpoint

GET https://app.tikk.chat/api/v1/bookings/{id}

Required scope: bookings.read

Path parameters

integer

required

The unique integer identifier of the booking to retrieve. Obtain this value from the id field on any Booking object returned by GET /bookings.

Example request

curl https://app.tikk.chat/api/v1/bookings/1234567 \
  -H "Authorization: Bearer {YOUR_API_KEY}"

Response schema

object

The matching Booking object.

Show Booking

integer

Unique booking identifier.

string

Current state of the booking. One of: pending, accepted, declined, cancelled.

string | null

The subject or agenda the booker provided when scheduling.

integer

Length of the meeting in minutes.

string (date-time) | null

UTC date-time the meeting is scheduled for. null while the booking has not yet been scheduled.

string (date-time) | null

UTC date-time the booking was first created.

string | null

Free-form notes attached to the booking.

string | null

The reason provided when the booking was declined or cancelled. null for all other statuses.

object

The person who made the booking.

Show booker fields

string | null

Booker’s display name.

string | null

Booker’s email address.

array

Additional seats on group bookings. Empty array for one-to-one meetings.

Show Attendee

string | null

Attendee’s display name.

string | null

Attendee’s email address.

object

The service this booking was made against.

Show service fields

string

URL-safe service identifier.

string

Human-readable service name.

boolean

true if multiple people can book the same time slot.

integer | null

Seat cap for group services. null for one-to-one or uncapped services.

boolean

true if this service was booked via a private link not listed on your public profile.

object

Where the meeting takes place.

Show location fields

string | null

One of video, in_person, none, or null.

string | null

Human-readable location name shown to the booker.

string | null

Physical address for in_person meetings. null for all other types.

string | null

Checkout URL for paid meetings while payment is still outstanding. null once payment is settled or for free meetings.

string | null

Video call URL sent to all participants. null for non-video meetings.

object

Payment state for this booking.

Show payment fields

string

One of: none, pending, paid, failed, refunded.

integer | null

Price in minor currency units. For example, 5000 equals €50.00. null for free meetings.

string

ISO 4217 currency code (e.g. EUR, USD).

Example response

{
  "data": {
    "id": 1234567,
    "status": "accepted",
    "topic": "Exploring a potential partnership",
    "duration_minutes": 30,
    "scheduled_at": "2026-08-19T12:00:00+00:00",
    "created_at": "2026-08-10T09:14:00+00:00",
    "notes": "Please bring your team's Q3 roadmap if possible.",
    "cancellation_reason": null,
    "booker": {
      "name": "Alex Kim",
      "email": "alex@example.com"
    },
    "attendees": [
      {
        "name": "Sam Rivera",
        "email": "sam@example.com"
      }
    ],
    "service": {
      "slug": "strategy-session",
      "title": "Strategy session",
      "is_group": true,
      "max_attendees": 5,
      "is_personal_invite": false
    },
    "location": {
      "type": "in_person",
      "label": "Brussels HQ",
      "address": "Rue de la Loi 42, 1000 Brussels, Belgium"
    },
    "meeting_link": null,
    "conference_link": null,
    "payment": {
      "status": "paid",
      "amount": 5000,
      "currency": "EUR"
    }
  }
}

Requesting an id that belongs to a booking in another user’s account returns 404, not 403. The API never confirms or denies that a booking outside your account exists, so you cannot enumerate other users’ booking ids through error codes.

Errors

Status	Meaning
`401`	Missing or invalid API key.
`403`	Your API key does not have the `bookings.read` scope.
`404`	No booking with the given `id` exists in your account. IDs belonging to other accounts also return `404`.
`429`	Rate limit exceeded. Back off and retry after the period indicated in the `Retry-After` header.

Overview

Endpoints

GET /bookings/{id}. Retrieve a single booking by ID

Endpoint

Path parameters

Example request

Response schema

Example response

Errors

​Endpoint

​Path parameters

​Example request

​Response schema

​Example response

​Errors

Endpoint

Path parameters

Example request

Response schema

Example response

Errors