# PUT /v1/owners-reservations/{} is deprecated

Guesty Open API deprecated PUT /v1/owners-reservations/{id} without giving a shutdown date yet.

On July 30, 2026, Guesty deprecated the PUT /v1/owners-reservations/{id} endpoint without a shutdown date. Calls to this endpoint will eventually fail once retired, though Guesty Open API noted that legacy reservation resources will continue to function until sunset.

## What to use instead

Use the dedicated v3 alteration endpoints (dates, guests, status, listing, notes) described in Guesty's Reservation Alterations guide.

- API: Guesty Open API (open-api.guesty.com)
- Kind: Endpoint removal
- Announced: July 30, 2026
- Takes effect: no date given yet
- Calls after that day: fail
- Calls it hits: `PUT /v1/owners-reservations/{id}`
- Source: [Announcement](https://open-api-docs.guesty.com/changelog/2026-07-30)
- Verified: November 6, 2026, against Guesty Open API's own pages
- Page: https://www.okapi.bot/providers/guesty-open-api/breaking-changes/put-v1-owners-reservations-is-deprecated/

## Guesty Open API's words

> Add deprecation tags and notices to the legacy reservation resources ahead of their retirement at the end of the year. They will continue to function until sunset.

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