Cancel a reservation where it lives

Reservations · POST /v1/reservations/:id/cancel

POST/v1/reservations/:id/cancel

Note

A booking managed in a connected PMS (Mews, Cloudbeds, Hostaway, Guesty, Beds24, BookingSync, Lodgify, Smoobu, Hospitable, iGMS) is cancelled in the PMS, then read back; no cancellation fee is charged, and Lodgify declines the booking rather than deleting it. OwnerRez cannot cancel through its API: 422 pms_write_unsupported, cancel it in OwnerRez. Direct, website and owner bookings: cancelled in Repull, releasing the nights, and reservation.cancelled fires. A channel booking (Airbnb, Booking.com, Vrbo), including one relayed through a PMS, is 409 reservation_owned_by_channel. Cancelling an already-cancelled reservation returns alreadyCancelled: true. A PMS refusal is 422 pms_rejected with the PMS reason. Guide: /docs/cancel-reservation

Request

curl -X POST https://api.repull.dev/v1/reservations/240230/cancel \
  -H "Authorization: Bearer $REPULL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "reason": "Guest asked to cancel" }'

Response

{
  "id": "240230",
  "confirmationCode": "M132552-0F5132F6",
  "listingId": "30610",
  "status": "cancelled",
  "checkIn": "2027-09-01",
  "checkOut": "2027-09-03",
  "pms": { "provider": "mews", "applied": ["cancel"], "errors": [] }
}

Body Parameters

reasonstring

Why it was cancelled; recorded on the reservation (and in the PMS notes).