# /v1/reservations/{}/custom-fields stops working

Calls to /v1/reservations/{id}/custom-fields* on Guesty Open API stopped working on May 31, 2026.

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.

## What to use instead

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.

- 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
- Calls it hits: `/v1/reservations/{id}/custom-fields*`
- Source: [Announcement](https://open-api-docs.guesty.com/docs/custom-reservation-fields-migration)
- Verified: November 6, 2026, against Guesty Open API's own pages
- Page: https://www.okapi.bot/providers/guesty-open-api/breaking-changes/v1-reservations-custom-fields-stops-working/

## 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.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent