Skip to main content
409 ConflictDeliveries

ACTION_NOT_ALLOWED

Not allowed in the current state

When it happens

The action conflicts with the object’s state. It happens when you: book a draft that isn’t priced (an address isn’t confirmed, or it is waiting for a price), is already booked or is cancelled; mark a delivered or cancelled delivery ready; ask for the label of a draft or a cancelled delivery; PATCH a cancelled delivery, or change pickup instructions after the pickup or drop-off instructions after the delivery; confirm an address that is already verified; call POST /wallet/fund with a test token or on an invoice account (or POST /sandbox/wallet/fund on an invoice account); or call POST /webhooks/test while Reeds has turned your endpoint off.

How to fix it

  1. Fetch the object and check its status and required_actions, clear what is outstanding, then retry with the same key.
RetryingRetry with the same Idempotency-Key.How idempotency works

Example response

HTTP 409 Conflict
{
"status": "failed",
"error": {
"code": "ACTION_NOT_ALLOWED",
"message": "Confirm the drop-off address before booking.",
"doc_url": "https://developer.getreeds.co/errors/ACTION_NOT_ALLOWED"
}
}