FAQ

What is the maximum number of properties that can be requested?

Travel Buyers can specify the limit value in the request.

• If no limit is provided, the API uses a default value of 100.
• The maximum supported limit is 1000.

What happens if some requested property IDs do not exist or are not accessible?

When using the Get Hotels by Property ID method, the API returns only the hotels that are available and accessible to the Travel Buyer.

For example:

• If 10 property IDs are requested
• And 1 property is invalid or inaccessible

The API will return the remaining 9 valid hotels.

No partial error is returned for missing or inaccessible properties.

How can Travel Buyers identify what changed for a hotel in incremental updates?

Currently, update statistics are only available at the global response level through fields such as:

• totalCount
• newCount
• updateCount
• deleteCount
• enableCount
• disableCount

At this time, the API does not indicate the specific change type for each individual hotel record.

Per-hotel change tracking is planned for a future API version.

Today, if a hotel shows up in the response when using incremental updates, travel buyers can check if the hotel exists in their system. If yes, update it. If no, create it.

Is there a maximum number of propertyIds allowed in a request?

Yes.

The maximum number of propertyIds supported is the same as the maximum supported limit value.

Current maximum: 1000

Should limit and resumeKey be used when requesting specific property IDs?

In most cases, limit and resumeKey are primarily intended for:

• Large property retrieval requests
• Incremental (since) synchronization workflows

However, it is still recommended to include a limit as a general best practice.

If the response exceeds the requested limit:

• A resumeKey will be returned for pagination.

If all results fit within the response:

• resumeKey will be null.

Is the meal plan list static?

The meal plan list is relatively stable, but new meal plans may be added over time.

Travel buyers should avoid hardcoding assumptions and periodically refresh mappings.