Guesty Open API · Endpoint removal
/v1/reservations/{}/custom-fields stops working
Stopped working
Calls to /v1/reservations/{}/custom-fields* on Guesty Open API stopped working on May 31, 2026.
What to use instead of these calls
Call the same operations under /v1/reservations-v3/{reservationId}/custom-fields (GET, PUT, and GET or DELETE /{fieldId}) and read the reservationId and customFields wrapper they return.
Calls it hits
/v1/reservations/{}/custom-fields*
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
More from Guesty Open API
- GET /v1/owners-reservations is deprecated Deprecated, no date
- GET /v1/owners-reservations/{} is deprecated Deprecated, no date
- GET /v1/reservations is deprecated Deprecated, no date
- GET /v1/reservations/{} is deprecated Deprecated, no date
- POST /v1/reservations is deprecated Deprecated, no date
- PUT /v1/owners-reservations/{} is deprecated Deprecated, no date