![]()
open-api.guesty.com · ProductivitySubscribeShare
Guesty Open API breaking changes
The breaking changes Guesty Open API announced that Okapi tracks: 8 in all.
Do you run the Guesty Open API? Make sure your users call it right →
At a glance
- API host
open-api.guesty.com- Kind
- Productivity
- Versions with breaking changes
- v1 (8)
- Breaking changes tracked
- 7 breaking changes with no date yet and 1 already in effect
- Last updated
Deprecated, no date yet 7
-
No date
GET /v1/owners-reservationsEndpoint removal Deprecated, no date -
No date
GET /v1/owners-reservations/{id}Endpoint removal Deprecated, no date -
No date
GET /v1/reservationsEndpoint removal Deprecated, no date -
No date
GET /v1/reservations/{id}Endpoint removal Deprecated, no date -
No date
POST /v1/reservationsEndpoint removal Deprecated, no date -
No date
PUT /v1/owners-reservations/{id}Endpoint removal Deprecated, no date -
No date
PUT /v1/reservations/{id}Endpoint removal Deprecated, no date
Already in effect 1
-
/v1/reservations/{id}/custom-fields*Endpoint removal Stopped working
Where Okapi reads it
- Changelog open-api-docs.guesty.com/changelog
- Announcement open-api-docs.guesty.com/changelog/2026-07-30
- Announcement open-api-docs.guesty.com/docs/custom-reservation-fields-migration
Know before your API calls break.
Okapi finds the calls a breaking change hits in your code and opens the pull request that fixes them.
Add to GitHub