We propose enhancing the /api/connector/v1/reservations/add endpoint to allow reservations for multiple properties to be processed in a single request. This functionality would enable guests to seamlessly make reservations across multiple properties, enhancing user experience and operational efficiency.

Currently, this is not possible because the endpoint requires ClientToken, AccessToken, and ServiceId at the root level, which ties the request to a single property. A possible solution could involve modifying the request body structure to include ClientToken, AccessToken, and ServiceId within each reservation. This would allow multiple property reservations to be handled in a single API call.

An alternative could be adding a dedicated endpoint designed to support multi-property reservations. This enhancement would align the API capabilities with real-world use cases involving multi-property management.

Thank you for considering this suggestion. We would be happy to discuss further if additional details or clarifications are needed.