Directions Service: Status Codes/Functional Maximums
The following tables describe the error messages that can be returned from an unsuccessful route request. Each function section also lists any functional maximums acceptable for that call.
Directions Service Call
| Status Code |
Description |
| 0 | A successful route call. |
| 400 | Error with input - The error message will start with: "Illegal argument from request:" followed by the specific error condition. |
| 403 | Key related error - The error message will attempt to explain why there was an error with the key and should provide a link to the Developer Network. |
| 500 | Unknown error - The error message will start with: "Error processing request:" followed by the message from the exception. |
| 600 - 699 |
Other error - Although the route request was valid, it could not be completed (e.g. because
the estimate route length exceeded the maximum allowed value). See the error message included
with the response for more details |
Route/Optimized Route Call
| Status Code |
Description |
| 601 | Invalid location specified. |
| 602 | The route failed, normally due to mustAvoidLinkIds options being set in a way that makes the route impossible. |
| 603 | No dataset found to calculate the route. |
| 610 | Ambiguities were found in one or more of the locations specified and ambiguities=ignore was not set. |
| Maximum |
Description |
| 50 | Number of locations acceptable. |
