pms_writes_off
The PMS connection's write policy turns off bookings through the API. Nothing was sent to the PMS. Turn on `reservations.api`, or make the change in the PMS.
When it fires
The listing is managed in a PMS, and that connection's write policy turns off bookings through the API (reservations.apiis off). Every create, change, cancel and quote on its listings answers this, and nothing is sent to the PMS. The listing's capabilities.reservations shows every flag false with the reason in notes.
The envelope's docs_url points to the write policy page, which explains every switch.
Response shape
Every Repull error follows the same envelope. The code is stable and safe to switch on.
{
"error": {
"code": "pms_writes_off",
"message": "Bookings for this property are managed in its PMS, and this connection is set not to change them through the API. Nothing was sent to the PMS.",
"fix": "Turn on `reservations.api` with `PATCH /v1/connect/{provider}/write-policy`, or make the change in the PMS.",
"docs_url": "https://repull.dev/docs/connect/write-policy",
"request_id": "req_01J5X7Y8Z9ABCDEF12345678"
}
}How to fix
- Decide whether your app should book in this PMS at all — the switch is usually off on purpose.
- If it should, turn it on: `PATCH /v1/connect/{provider}/write-policy` with `{"reservations": {"api": true}}`, then retry.
- Otherwise make the change in the PMS; it reaches Repull with the next sync.
Examples
curl
curl -X PATCH https://api.repull.dev/v1/connect/cloudbeds/write-policy \
-H "Authorization: Bearer sk_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"reservations": {"api": true}}'TypeScript
const { error } = await res.json()
if (error?.code === 'pms_writes_off') {
// A deliberate setting — surface it rather than flipping it automatically
return { writesOff: true, howToEnable: 'PATCH /v1/connect/{provider}/write-policy' }
}If you're an AI agent
The PMS connection is configured not to accept booking writes from the API. Do not retry and do not change the policy without the user's consent. Ask the user whether to enable reservations.api via PATCH /v1/connect/{provider}/write-policy, or to make the change in the PMS.
Related
- Error reference — the full table of error codes
- Using Repull from AI agents — patterns for handling errors in agent loops
- PMS write policy
- Creating reservations
Hit an error that isn't covered? Email hello@repull.dev with the request id from the response headers.