{id} endpoint removal

Deprecated, no dateSubscribe to Guesty Open APIShare

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.

Calls it hits

PUT /v1/owners-reservations/{id}

What to use instead of these calls

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

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

Guesty Open API, Announcement

Facts

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
Source: Announcement
Last updated: October 25, 2026
Verified: November 6, 2026, against Guesty Open API's own pages

Questions

When does this change take effect?

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

Do these calls still work?

Yes, they still work: Guesty Open API has not given a shutdown date yet.

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.

Is your code calling this?

Okapi finds the calls this change hits in your repo and opens the pull request with the fix.

Add to GitHub