signs-postIntegration Requirements

Understand what your integration must implement before connecting to production.

These requirements define the technical standards your integration must meet to work correctly with the Direct Booking API. Work through each section during your build — not after.

Limitations

This API is only available to hotel groups on Multi-Property with the SiteMinder Platform. Groups on the classic version of the SiteMinder Channel Manager will not be able to access the Direct Booking API.

Authentication

Every request must include a valid API key in the x-sm-api-key header.

Do not pass the key as a query parameter or embed it in client-side code.

Intended Use

This API is intended to be used for server-to-server communications only. It is not intended to be used from a front-end web page as this will expose your secret key to the public and may also allow the API keys' rate limit to be exceeded and prevent API access.

Rate Limit

Each key is limited to 100 API calls per minute. Your integration must handle 429 responses with exponential backoff. Do not retry immediately, wait until the next minute.

Pagination

Responses from list endpoints are paginated. Your integration must not assume all results are returned in a single response.

  • Iterate through pages using the page parameter.

  • Continue until page equals totalPages.

  • Default page size is 10, adjust using perPage.

Stay Length Limit

Availability queries via /quotes must not exceed 31 days per request. Split longer date ranges across multiple requests.

Error Handling

Your integration must handle all error responses gracefully. Do not surface raw API error messages to guests.

Data Freshness

The data is kept up to date as inventory is booked and changes are made to your configuration in Direct Booking. Avoid caching responses for extended periods to prevent stale availability being shown to guests.

sparkles

Still have questions?

Last updated

Was this helpful?