reservation_not_modified
The change was refused for a booking reason, for example a move to a listing that cannot take it. Nothing was changed; `message` says why.
HTTP 422The request was understood but refused as sent. Change it before retrying.
When it fires
A change through PATCH /v1/reservations/{id} on a booking that is not managed in a PMS was refused for a booking reason — for example a move to a listing that cannot take the stay. Nothing was changed; message says why.
Response shape
Every Repull error follows the same envelope. The code is stable and safe to switch on.
{
"error": {
"code": "reservation_not_modified",
"message": "<why the change was refused>",
"fix": "See https://repull.dev/docs/errors for recovery steps.",
"docs_url": "https://repull.dev/docs/errors/reservation_not_modified",
"request_id": "req_01J5X7Y8Z9ABCDEF12345678"
}
}How to fix
- Read `message` for the reason.
- Adjust the change (other dates, another listing) and send it again.
Examples
curl
curl -X PATCH https://api.repull.dev/v1/reservations/215710 \
-H "Authorization: Bearer sk_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"listingId": 4119, "checkIn": "2026-10-02", "checkOut": "2026-10-06"}'TypeScript
const { error } = await res.json()
if (error?.code === 'reservation_not_modified') {
return { refused: true, reason: error.message } // nothing changed
}If you're an AI agent
The change was refused and nothing changed; `message` gives the reason. Adjust the requested change rather than repeating it.
Related
- Error reference — the full table of error codes
- Using Repull from AI agents — patterns for handling errors in agent loops
- Update a reservation
Hit an error that isn't covered? Email hello@repull.dev with the request id from the response headers.
AI