Update a Delivery Customer
PUT/delivery/customers/:customer_id
Updates the details of an existing delivery customer. Sending client_reference as null clears it, including on the customer's pending stops. A key that is not sent is left unchanged. Changing country_id requires an address field (address_line_1, address_line_2 or postal_code) or both latitude and longitude in the same request, otherwise the request is rejected with HTTP 422.
A write that ends in a 500 "Server Error" or a 502 "Bad Gateway" has an unknown outcome, so it may have been saved. Before you retry, check the current state with GET /delivery/customers/{customer_id}.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 422
- 500
- 502
- 503
Successful operation
The request body is declared as JSON but cannot be parsed, or is not a JSON object or array. Nothing was processed.
Unauthorized access. Authentication is required.
Access is forbidden. The user does not have permission to access this resource. Delivery write endpoints also return this error when the request is authenticated with a subuser api_key, which cannot write to Delivery; in that case error.message is Unauthorized and error.data.message is Unauthorized for this role. Authenticate with the main account's api_key and, where supported, set the subuser_id body field to act on behalf of a subuser.
The requested resource was not found.
Validation failed for the input parameters.
Server Error. The request could not be processed, so the API may need more time to process it. The response has error.message "Server Error" and an error.reason that classifies the failure, for example "dependency_unavailable" or "internal_error". New values may be added over time, so treat an unrecognised error.reason as a generic server error. The outcome of a write is unknown, so it may have been saved. Before you retry, check the current state with GET /delivery/customers/{customer_id}.
Bad Gateway. The request could not be completed because a service needed to process it returned an error. The response has error.message "Bad Gateway" and error.reason "upstream_error". The outcome of a write is unknown, so it may have been saved. Before you retry, check the current state with GET /delivery/customers/{customer_id}.
Service temporarily unavailable. The request did not complete and can be retried after the number of seconds in the Retry-After header, when one is sent.
Response Headers
Seconds to wait before retrying. Sent with db_busy and db_pool_timeout.