HTTP Request Headers
Important context information is passed to the Places (Search) API using optional HTTP request headers. Wherever applicable the service relies on established and standardized headers, complementing these with some additional private headers. Some of these directly affect the results, while others help to optimize search results.
Note: Headers below are also accepted as GET url parameters of the same names. This functionality is provided only for developer convenience when experimenting with Places (Search) API in a web-browser. Production applications should not rely on this and should always send headers with each request as defined by HTTP standards.
| || Specifies which media types are acceptable for the response (see Accept header specification ). This header is ignored for JSONP requests, which always have an |
| || The user or client's preferred languages (see Accept-Language header specification). This value is used to select the language of content in the response. Default: |
Note: When different from default, the desired language must be specified in
| || The user's local time, for example, |
| ||A string identifying the client user agent (see User-Agent header specification), used for statistical purposes. If the Places (Search) API is accessed from within a web browser, the browser should send this information automatically. For other applications, it may need to be explicitly set by the application.|
| || Allows clients to enable compressed transfer of responses. The only supported value is |
| ||The user's current position, formatted as a 'geo' URI as described in the Position Format documentation. (see HTTP Geolocation Internet-Draft). In the absence of an explicit location context, this is used to calculate the distance from the user returned in place results, and can act as an implicit location context. To ensure the best results possible, client applications should always send this header if it is able to determine the user's position.|
| ||The bounding box of the map area currently visible to the user, formatted as described in the Bounding Box Format documentation. The viewport can act as an implicit location context in the absence of an explicit location context. To ensure the best results possible, client applications should always send this header if it is able to determine the user's position.|
| || This header allows an application to indicate the user's means of transport, which can help Places (Search) API return better results: |
| || If an application is using HERE map tiles and displaying a specific version of the tiles, the application can specify the map version using this header to ensure that returned place coordinates match the tiles you are using. The header value has the form |
| || Used signal that a request is a test request, which won't influence our search relevance model. |
| ||Specify the political view. Available territories will be seen through the point of view of this country. If this parameter is not specified the neutral international view is made available, where territories may have unresolved claims. The country of the view is to be specified as ISO 3166-1-alpha-3 string.|
| ||If request originates from motor vehicle, this header can be used to specify the Vehicle Identification Number (VIN) as per ISO 3779|