2026-07-30 - Mark legacy resources for deprecation

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 will provide guidance and a migration schedule at the start of the deprecation period.

Changed

• 16 legacy /reservations and /owners-reservations operations are now marked deprecated: true, with descriptions updated to point to their v3/beta replacements where applicable:
  • POST /reservations — Quick booking or quote and confirm
  • GET /reservations (search) → v3 search reservations
  • GET /reservations/{id} → v3 get-reservations-by-ids
  • PUT /reservations/{id} → dedicated v3 endpoints (dates, guests, status, listing, notes, etc.), see Reservation Alterations guide
  • POST /reservations/{id}/payments → TBA
  • PUT /reservations/{id}/payments/{paymentId} → TBA
  • POST /reservations/{id}/payments/{paymentId}/refund → TBA
  • PATCH /reservations/{id}/payments/{paymentId}/cancel → TBA
  • POST /reservations.csv (already deprecated: true) → Use Get report or v3 search reservations
  • POST /reservations.email (already deprecated: true) → Use Get report or v3 search reservations
  • POST /reservations/{id}/approve → v3 approve-channel-reservation
  • POST /reservations/{id}/decline → v3 decline-channel-reservation
  • POST /reservations/{id}/request-cancellation-sync → v3 request-cancellation-channel-reservation
  • GET /owners-reservations → Retrieve reservations
  • GET /owners-reservations/{id} → Retrieve reservations
  • PUT /owners-reservations/{id} → dedicated v3 endpoints (dates, guests, status, listing, notes, etc.), see Reservation Alterations guide