---
title: "Get all booking tickets"
method: GET
path: "/booking-tickets"
tags: ["Booking tickets"]
---

# Get all booking tickets

`GET /booking-tickets`

Get a list of all booking tickets. A booking ticket defines a type of bookable resource or service - for example, a therapist, a consultation room, or an event. Use filters such as `customer_id`, validity range, or ticket properties to narrow results.

## Query parameters

- `count` integer
- `offset` integer
- `sort_field` string
- `sort_direction` 'ASC' | 'DESC'
- `customer_id` string
- `valid_from` string
- `valid_to` string
- `valid_only` true | false
- `booking_ticket_property_id` string
- `booking_ticket_property_value` string

## Headers

- `Accept-Language` string

## Response `200`

OK

- object
  - `data` object
    - `booking_tickets` BookingTicket[] — Collection of booking tickets.
      - `ticket_id` string — The unique ID of the booking ticket.
      - `name` string, required — Name of the booking ticket in language from request header.
      - `created_at` string — Timestamp of the ticket creation. Accepts the format `YYYY-MM-DD HH:MM:SS` or ISO-8601 format (`YYYY-MM-DDTHH:MM:SS`). All times must be in the local timezone.
      - `valid_from` string — Timestamp from which the ticket is valid. Accepts the format `YYYY-MM-DD HH:MM:SS` or ISO-8601 format (`YYYY-MM-DDTHH:MM:SS`). All times must be in the local timezone.
      - `valid_to` string — Timestamp until which the ticket is valid. Accepts the format `YYYY-MM-DD HH:MM:SS` or ISO-8601 format (`YYYY-MM-DDTHH:MM:SS`). All times must be in the local timezone.
      - `state` 0 | 1 — State of the booking ticket. *Possible values are: 0 - blocked / 1 - active*
      - `last_change` string — Date and time of the last change. *(YYYY-MM-DD HH:MM:SS)*
    - `total_items` integer — The number of all found booking tickets.

## Other responses

- `400` — Bad input parameter. The response body's `error.error_data.invalid_params[]` array lists the parameters that caused the failure, each carrying a `reason` code. See the `BadRequestErrorBody` schema for the generic reason taxonomy. Operations with domain-specific business rules document additional reasons at the operation level.
- `401` — The client has invalid credentials or auth token.
- `403` — The client does not exist or the client tried to access an unauthorized property or resource.
- `404` — The resource was not found.
- `405` — The resource does not support the specified HTTP method.
- `429` — Too many requests - more than the resource limit.
- `500` — Server is not working as expected.
- `503` — Temporary state when the service is temporarily unavailable, overloaded or there is a maintenance window.

---

[API](https://skmtc.net/crmcarecloud/apis/rest-api-reference.md) · [All operations](https://skmtc.net/crmcarecloud/apis/rest-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/crmcarecloud/rest-api-reference/revisions/329c06dbf8d9/schema)