Request tracing in HERE Routing API v8

When submitting a bug report or asking for support for specific route calculations, always provide the routing request URI, request identifiers, and the corresponding errorCode, if any.

X-Request-ID

You can tag your requests with a request identifier using the non-standard HTTP header X-Request-Id. The service will forward this value to the response, be it a success or a failure. If no value is provided, a UUID will be generated on the incoming request and this value will be attached to the response as the X-Request-Id. While you can use any string as the request identifier, it's recommended to use a UUID to uniquely identify your requests or group of requests.

X-Correlation-Id

In addition to the X-Request-Id HTTP header, the service response will also carry a X-Correlation-Id HTTP header. This is an auto-generated unique identifier that is unique to every request.

Use cases

• You can specify either the X-Request-Id or X-Correlation-Id when filing a bug or posting a question about a specific request to support channels.
• You can tag a group of correlated requests with the same X-Request-Id to identify the correlation.
• If you have your own request tracing identifier, you can pass this value as the X-Request-Id to continue the tracing through the service.