# POST /v1/reservations is deprecated

Guesty Open API deprecated POST /v1/reservations without giving a shutdown date yet.

Guesty Open API has deprecated POST /v1/reservations without an exact shutdown date, though notices indicate retirement at the end of the year. Calls to this endpoint will continue to function until sunset, after which they will fail.

## What to use instead

Create a quote with POST /v1/reservations-v3/quote and confirm it with POST /v1/reservations-v3, or use the quick owner booking endpoint.

- 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: `POST /v1/reservations`
- 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/post-v1-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