---
title: "Get reservation channel manager details"
method: POST
path: "/api/connector/v1/reservations/getChannelManagerDetails"
tags: ["Reservations"]
---

# Get reservation channel manager details

`POST /api/connector/v1/reservations/getChannelManagerDetails`

Returns channel manager-related details for the specified reservations. Note this operation supports [Portfolio Access Tokens](https://mews-systems.gitbook.io/connector-api/concepts/multi-property/).

## Request body

- ReservationsChannelManagerDetailsFilterParameters
  - `ClientToken` string, required — Token identifying the client application.
  - `AccessToken` string, required — Access token of the client application.
  - `Client` string, required — Name and version of the client application.
  - `ReservationIds` string[], required — Unique identifiers of the `Reservations`.

## Response `200`

OK

- ReservationsChannelManagerDetailsResult
  - `ChannelManagerDetails` ChannelManagerDetails[], required — List of reservation channel manager details.
    - `ReservationId` string, uuid, required — Unique identifier of the `Reservation`.
    - `RequestedRateCode` string, required — Rate code requested by the channel manager for this reservation.
    - `ChannelManagerName` string, nullable — Name of the Channel Manager associated with this reservation.
    - `ChannelNumber` string, nullable — Number of the reservation within the Channel (i.e. OTA, GDS, CRS, etc) in case the reservation group originates there (e.g. Booking.com confirmation number).
    - `ChannelManagerGroupNumber` string, nullable — Number of the reservation group within a Channel Manager.
    - `ChannelManagerNumber` string, nullable — Unique number of the reservation within the reservation group.
    - `CreatedUtc` string, date-time, required — The timestamp when the Channel Manager reservation was created.

## Other responses

- `204` — Server has successfully fulfilled the request and there is no additional information to send back.
- `400` — Error caused by the client app, e.g. in case of malformed request or invalid identifier of a resource. In most cases, such an error signifies a bug in the client app (consumer of the API).
- `401` — Error caused by usage of invalid ClientToken, AccessToken, or you may not have the necessary permission to use the endpoint.
- `403` — Server error that should be reported to the end user of the client app. Happens for example when the server-side validation fails or when a business-logic check is violated.
- `408` — Error caused by heavy request that takes too long to process (typically tens of seconds). To get around this, request data in smaller batches. For more information, see [Request timeouts](https://mews-systems.gitbook.io/connector-api/guidelines/requests#request-timeouts)
- `429` — Error caused by too many requests sent in a given amount of time. Response contains `Retry-After` header indicating how long the user agent should wait before making a follow-up request. For more information, see [Request limits](https://mews-systems.gitbook.io/connector-api/guidelines/requests#request-limits).
- `500` — Unexpected error on the Mews side. This may be due to a software fault. If such a situation occurs, the error will be logged and the development team notified, however you can raise an issue through GitHub on our [documentation repository](https://github.com/MewsSystems/gitbook-connector-api).

---

[API](https://skmtc.net/mews/apis/connector-api.md) · [All operations](https://skmtc.net/mews/apis/connector-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mews/connector-api/revisions/eb29e5887d8a/schema)