Traffic API Developer's Guide

HTTP Status Codes

Traffic API supports the standard HTTP status codes.

Table 1. HERE Error Codes
Error code	Description
200 OK	Indicates success, but may also be returned when an invalid resource name and/or an invalid parameter combination has been used in the request.
204 No Content	Indicates that the request was valid but there is no traffic data available.
400 Bad request	Invalid parameter value in the request, for example `zoom` out of range. Examples include: The quadkey parameter is invalid ([length] 22 or any character not in [0,1,2,3]). The required parameters are not provided. The query combines both bbox and quadkey parameters, which is not permitted. You must use either the bbox or quadkey parameter. An invalid bbox parameter format. The bbox parameter must be specified in the form [lat0],[lon0];[lat1],[lon1] Incorrect values for the filtering parameters were used.
403 Forbidden	Missing or incorrect API Key in the request. If you are using `token` authentication, the `token` that you use in the request is incorrect. For more information on authentication, see the Identity & Access Management Developer Guide.
404 Not found	Unsupported parameter in the request. Examples include: The domain-section of the URL does not point at a valid service environment. The path-section of the URL does not point at a quadkey service instance.
500 Internal error	The service is not available or server configuration issue.
503 Service Unavailable	Indicates that the services is temporarily unavailable due to system overload or maintenance

The API supports the standard authorization mechanism common to all HERE APIs. This mechanism can return status codes detailed below.

Table 2. Authentication Responses
Scenario	Response Code	HTTP Response Message
`apiKey` is missing	400	The request is missing the `apiKey` parameter. Note: If you are using `app_id`/`app_code` authentication, the `app_id` and `app_code` parameters are missing. They must both be passed as query parameters. For the available authentication options, see the Identity & Access Management Developer Guide.
`apiKey` is present in the request but the validation fails.	401	This is not a valid `apiKey`. Note: If you are using `app_id`/`app_code` authentication, please verify that the values are not swapped between the `app_id` and `app_code`. For the available authentication options, see the Identity & Access Management Developer Guide.
No matching pattern in the authentication mechanism configuration for this requested URL	404	The URL resource cannot be found.
If the requested URL does exist but the HTTP verb is not supported for that URL	405	The HTTP method is not supported for this URL.
If SSL is required, but the request is not sent over SSL.	400	SSL/TLS is required for this URL; please retry the request using SSL/TLS.
Unexpected authentication error	500	Server error - please retry again at a later time.