xpand OAuth API for Reservation Times, Notes, To Dos, and Airbnb Review Details

We use the iGMS OAuth API as part of an automated property-management integration and would like to reduce our dependence on browser/UI automation.

We are requesting supported OAuth API access for several reservation functions that are currently available in the iGMS user interface but do not appear to have equivalent documented API methods.

Requested functionality

1. Expected check-in time

• Read the current expected check-in/arrival time

• Update the expected check-in/arrival time

The existing bookings API already returns local_checkin_dttm, so ideally there would be a supported method to update that same reservation value.

2. Expected checkout time

• Read the current expected checkout/departure time

• Update the expected checkout/departure time

The existing bookings API already returns local_checkout_dttm, so ideally there would be a supported method to update that same reservation value.

3. Reservation Thread To Do

• Read the current Thread To Do

• Create/update the Thread To Do

• If applicable, clear/archive a completed Thread To Do

4. Reservation Note

• Read the existing Reservation Note

• Create/update or append to the Reservation Note

5. Airbnb review details
For Airbnb reservations/reviews, expose the detailed review information available in iGMS, including the individual category ratings where available:

• Cleanliness

• Accuracy

• Check-in

• Communication

• Location

• Value

We would also like access to the associated overall review/rating and review text through the API where available.

Read-after-write verification

For every API write operation, it is very important to us that there also be a corresponding read method.

Our integration is designed to verify the exact resulting state after a write rather than assuming that an HTTP success response means the requested state was actually applied.

For example:

1. Read the current reservation state.

2. Submit the update.

3. Read the reservation again.

4. Verify that the intended field now contains the expected value.

This is particularly important for expected arrival/departure times, Notes, and To Dos.

OAuth permissions

Ideally these functions would be exposed through documented OAuth scopes, with separate read and write permissions where practical so integrations can follow least-privilege security practices.

Use case

Our integration, L.U.C.A.S., automates parts of our vacation-rental operations across Airbnb, Vrbo, Direct Bookings, and iGMS.

We already have an approved iGMS API client and use supported API/webhook methods wherever possible. Several remaining workflows still require browser automation solely because the corresponding iGMS UI functionality is not exposed through the OAuth API.

Adding these endpoints would allow us to:

• reduce fragile browser automation;

• improve reliability;

• use least-privilege OAuth authorization;

• positively verify changes after writes;

• avoid duplicate or uncertain actions;

• make iGMS the supported system interface rather than automating the web UI.

We would be happy to test beta access or provide additional technical details about our use case if these capabilities are considered for the API roadmap.