The pricing-management scope is provisioned only to partner platforms that generate their own price suggestions. It is not part of the public scope list and is not granted on request: an integration qualifies for it only by producing price and minimum-stay suggestions of its own, which iGMS then presents to the user for review or applies automatically depending on the property setting.
The scope grants access to view calendar data and to suggest prices and minimum stay. Apps holding it use these endpoints:
| Endpoint | Purpose |
|---|---|
| v1/propose-calendar-data | Suggest calendar data for a continuous period |
| v1/propose-calendar-batch | Suggest calendar data for separate days |
| v2/set-property-calendar-control | Enable or disable calendar control for the app on a property |
| v1/get-calendar-data | Read the calendar data the suggestions are based on |
| v1/listings | List of listings managed by the company |
| v1/bookings | List of active bookings |
| v1/hosts | List of all hosts |
The first three endpoints are exclusive to this scope, and their pages are reachable only through the links above: they are absent from the site navigation and from the list of methods. The four read endpoints are shared with other scopes, so their own pages list the scopes an ordinary app needs for them and do not mention pricing-management; this scope grants access to them all the same.
The scope also affects two read endpoints available to every app: v1/get-properties and v1/get-property add the calendar_control_allowed field to the response only for apps holding this scope. The field reports whether the user has allowed the app to apply suggestions to that property directly instead of saving them for review.
Webhooks available with this scope: booking_data, calendar_data, properties_data, property_calendar_control_changed.