---
title: "Get an entrance"
method: GET
path: "/entrances/{entrance_id}"
tags: ["Charged entrances"]
---

# Get an entrance

`GET /entrances/{entrance_id}`

Get information about a specific entrance resource.

## Path parameters

- `entrance_id` string, required

## Headers

- `Accept-Language` string

## Response `200`

OK

- object
  - `data` Entrance — Entrance structure.
    - `entrance_id` string, required — The unique ID of the entrance.
    - `pos_id` 3 | 6 | 9 | 11, required — ID of POS system for tickets. Required with path parameter entrance ID. *Possible values are: EPOS - 3 / skidata - 6 / axess - 9 / base - 11*
    - `name` string — Name of the entrance.
    - `customer_id` string — The unique ID of the customer. [GET /customers](https://carecloud.readme.io/reference/getcustomers)
    - `resort_name` string — Name of the resort where the entrance is charged.
    - `customer_category_name` string — Name of the customer category.
    - `external_order_id` string — ID of an external order created in the POS system.
    - `external_entrance_id` string — External ID of the entrance. Structure can be different depending on the POS system that created the entrance.
    - `external_turnstile_permission_id` string — External ID of the permission to open a turnstile. Structure can be different depending on the POS system that created the permission.
    - `entrance_type_id` 0 | 1 | 2 — Type of the entrance. *Possible values are: season ticket - 0 / one day ticket - 1 / multiple day ticket - 2*
    - `order_item_id` string — Order ID item represents relation between entrance and order item from carecloud e-shop.
    - `card_id` string, required — The unique ID of the card used to charge the entrance. [GET /cards](https://carecloud.readme.io/reference/getcards)
    - `created_at` string — Timestamp of the entrance creation in CareCloud. Format: `YYYY-MM-DD HH:MM:SS`. All times are in the local timezone.
    - `cancelled_at` string — Timestamp of the entrance cancellation in CareCloud. Format: `YYYY-MM-DD HH:MM:SS`. All times are in the local timezone.
    - `charged_price` number, float — Price charged to POS system.
    - `product_ids` string — The unique ID of the product. [GET /products](https://carecloud.readme.io/reference/getproducts)
    - `charge_date` string — Timestamp when the entrance will be or was charged to the POS system. Format: `YYYY-MM-DD HH:MM:SS`. All times are in the local timezone.
    - `valid_from` string — Date of the first day when the customer can use the entrance in ISO-8601 format (`YYYY-MM-DD`).
    - `valid_to` string — Date of the last day when the customer can use the entrance in ISO-8601 format (`YYYY-MM-DD`).
    - `last_change` string — Timestamp of the last change. Format: `YYYY-MM-DD HH:MM:SS`. All times are in the local timezone.
    - `state` 0 | 1, required — State of the entrance. *Possible values are: 0 - cancelled / 1 - active*

## 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)