Retrieve Configurations

get

{baseUrl}/configurations

⚠️
Outbound contract (Resly → partner)
Resly calls your API with this request. You do not call Resly. Host a GET /configurations receiver so Resly can load room types and rate plans when a channel account is linked or refreshed.

Resly sends channelAccountCode as a query parameter and authenticates with HTTP Basic.

Respond with 200 and a JSON body whose channelAccountCode exactly matches the query value, plus channelAccountName and nested channelRoomTypes / channelRatePlans.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

⚠️
Outbound contract (Resly → partner)
This page documents a request that Resly sends to your API, not an endpoint you call on Resly. Implement a receiving GET /configurations on your base URL so Resly can pull room types and rate plans when a channel account is linked or refreshed.

Resly uses the response to populate channel mapping in Resly PMS. See the OpenAPI request/response below for the exact query parameter, auth, and JSON shape Resly sends and expects.

Responses

Outbound contract (Resly → partner) This page documents a request that Resly sends to your API, not an endpoint you call on Resly. Implement a receiving GET /configurations on your base URL so Resly can pull room types and rate plans when a channel account is linked or refreshed.

200Configuration for the requested channel account.

400Invalid or unknown channelAccountCode, or malformed request.

401Authentication failed (invalid Basic credentials).

Outbound contract (Resly → partner)
This page documents a request that Resly sends to your API, not an endpoint you call on Resly. Implement a receiving `GET /configurations` on your base URL so Resly can pull room types and rate plans when a channel account is linked or refreshed.