In preparation for extreme weather conditions we have been working with our tech team to create automations that will improve our current processes and client communication.
One of them involves the ability to close specific delivery areas if the supply is too low and to display a message to inform you that a zone is closed if you create a job within this specific area. The key aims are to be transparent and to create smoother processes for you and your end-customers by ultimately improving expectation management all round.
In order to do so, we will need you to implement a minor change to your current API implementation. Everything is explained in the API documentation: a new error code is available in response of the Job creation endpoint and eta endpoint. When the corresponding area is closed for delivery you’ll receive a 422 HTTP response code with the following body:
{
"error": "LOCATION_TEMPORARILY_UNAVAILABLE",
"message": "We cannot operate in this area at the moment, please try again later"
}
Response codes available in the API documentation for both endpoint has also been updated.