Guesty Open API
/v1/reservations/{id}/custom-fields* endpoint removal
Stopped workingSubscribe to Guesty Open APIShare
On May 31, 2026, Guesty permanently removed the Custom Reservations Fields v2 resource. Calls to /v1/reservations/{id}/custom-fields* fail since that day. Requests to these endpoints are no longer supported.
Calls it hits
/v1/reservations/{id}/custom-fields*
What to use instead of these calls
Call the same operations under /v1/reservations-v3/{reservationId}/custom-fields for GET, PUT, and GET or DELETE /{fieldId}. The transition requires updating your integration to read the reservationId and customFields wrapper returned by the new endpoints.
In Guesty Open API's words
After this date, the Custom Reservations Fields v2 resource will be permanently removed, and all associated API calls will fail.
Facts
- API
- Guesty Open API
open-api.guesty.com - Kind
- Endpoint removal
- Announced
- November 20, 2025
- Takes effect
- May 31, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Guesty Open API's own pages
Questions
When does this change take effect?
Calls to /v1/reservations/{id}/custom-fields* on Guesty Open API stopped working on May 31, 2026.
What happens to calls after May 31, 2026?
They have failed since May 31, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Guesty Open API 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
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.