Change a reservation's dates, occupancy or listing
Reservations · PATCH /v1/reservations/:id
Change a reservation's dates, occupancy or listing
PATCH
/v1/reservations/:idNote
A stay managed in a connected PMS is changed in the PMS first, then refreshed from its record: checkIn, checkOut and guestCount change; a listing move, new times, or anything the PMS API cannot change (e.g. dates on Smoobu) is 422 pms_write_unsupported; taken dates are 409 pms_unavailable; the outcome is in pms. A channel booking is 409 reservation_owned_by_channel; a group booking in the PMS is 409 pms_group_booking. Guest details, pricing, status, platform and notes are refused by name (422 unsupported_field). Direct bookings are changed in Repull and reservation.updated fires. Guide: /docs/update-reservation
Request
curl -X PATCH https://api.repull.dev/v1/reservations/456 \
-H "Authorization: Bearer $REPULL_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"checkIn": "2026-10-02",
"checkOut": "2026-10-07",
"guestCount": 3
}'Response
{
"id": "215708",
"confirmationCode": "HA-4471923",
"listingId": "4118",
"checkIn": "2026-10-02",
"checkOut": "2026-10-06",
"checkInTime": null,
"checkOutTime": null,
"status": "confirmed",
"updatedAt": "2026-09-30T14:30:00Z",
"changed": ["checkIn", "checkOut", "guestCount"],
"pms": { "provider": "hostaway", "reservationId": "4471923", "applied": ["dates", "guests"], "errors": [], "partial": false, "failedSections": [] }
}Body Parameters
checkIndatecheckOutdatecheckInTimestringcheckOutTimestringguestCountintegerlistingIdintegerMove the reservation to another property in this workspace. Combined with dates, it is applied as ONE move so the access code is re-issued once.
AI