HERE Map Tile v2 Developer's Guide

Constructing a Request

A typical request to the HERE Map Tile v2 includes the basic elements shown in the following table and may contain resource-specific parameters or data.

Table 1. Basic request elements
Element	Value/Example	Description
Base URL	Aerial Tiles `https://{1-4}.aerial.maps.ls.hereapi.com` Base Map Tiles `https://{1-4}.base.maps.ls.hereapi.com` Traffic Tiles `https://{1-4}.traffic.maps.ls.hereapi.com`	Production environment See also Load Balancing and URLs
Legacy Base URL	Traffic Tiles `https://{1-4}.aerial.maps.api.here.com` Traffic Tiles `https://{1-4}.base.maps.api.here.com` Traffic Tiles `https://{1-4}.traffic.maps.api.here.com`	Production environment when you use an app_id/app_code pair. For more information, see Load Balancing and URLs. For the available authentication options, see the Identity & Access Management Developer Guide.
Path	`/maptile/2.1/`
Resource (tile type)	`alabeltile`: aerial or base map ^[1] `basetile`: aerial or base map ^[1] `blinetile`: aerial or base map ^[1] copyright ^[1] flowbasetile ^[3] flowlabeltile ^[3] flowtile ^[3] info ^[2] `labeltile`: aerial or base map ^[1] `linetile`: aerial or base map ^[1] `lltile`: aerial or base map ^[1] `mapnopttile`: aerial or base map ^[1] `maptile`: aeriel or base map ^[1] meta/pois meta/pviews `streettile`: aerial or base map ^[1] traffictile ^[3] `trucknopttile`: aerial or base map ^[1] `truckonlytile`: aerial or base map ^[1] `trucktile`: aerial or base map ^[1] version ^[1] `xbasetile`: aerial or base map ^[1]	GET only. For a more detailed parameter list for each resource, see API Reference.
Map version	newest (example)	Specifies the map version, either `newest` or with a `hash` value. See also Map Versions.
Scheme	normal.day (example)	Specifies the view scheme. A complete list of the supported schemes may be obtained by using the Info resource. Note: Be aware that invalid combinations of schemes and tiles are rejected. For all `satellite`, `hybrid` and `terrain` schemes, you need to use the Aerial Tiles base URL instead of the normal one. For the `hybrid.traffic.day` scheme, you need to use the Traffic Tiles base URL instead of the normal one. Traffic Tiles and Map Tiles support the other traffic related schemes (`normal.traffic.day`, `normal.traffic.night`). In order to properly support the traffic overlay case where you would request a transparent traffic tile from Traffic Tiles and a base tile from Map Tiles, the Map Tiles also support these schemes, in addition to Traffic Tiles supporting them.
Zoom	13 (example)	Zoom level of the map image. Minimum and maximum zoom levels are specified in the Info resource.
Column	4400 (example)	`col` – can be any number between 0 and `number of columns - 1`, both inclusive. The number of tiles per column is a function of the zoom: `number of columns = 2^zoom`
Row	2686 (example)	`row` – can be any number between 0 and number of rows - 1, both inclusive. The number of tiles per row is a function of the `zoom`: `number of rows = 2^zoom` .
Size	256 (example)	Returned image size. The following sizes ([width, height]) are supported: `256` = [256, 256] `512` = [512, 512] The following sizes ([width, height]) are deprecated, although usage is still accepted: `128` = [128, 128] Note: Raster coverage tiles (`rctile`, `rconlytile` and `rcdistonlytile`) only support 256 sizes.
Format	png8 (example)	Returned image format. The following image formats are supported: `png` – PNG format, 24 bit, RGB `png8` – PNG format, 8 bit, indexed color `jpg` – JPG format at 90% quality Please note that JPG is recommended for `satellite` and `hybrid` schemes only.
API Key	`?apiKey={YOUR_API_KEY}`	Substitute your own unique `apiKey`. For more information on authentication, see the Identity & Access Management Developer Guide.
Application Code - Legacy	`&app_code={YOUR_APP_CODE}`	Substitute your own unique `app_code`. For more information on authentication, see the Identity & Access Management Developer Guide.
Application ID - Legacy	`&app_id={YOUR_APP_ID}`	Substitute your own unique `app_id`. For more information on authentication, see the Identity & Access Management Developer Guide.
Resource Specific Parameters	`&{parameter=value}`	Optional Query Parameter. Refer to the API definition for values.

Notes:

[1]	Use the right base URL depending on what kind of tiles you want to get. Keep in mind that for some `schemes` you should use different base URLs. For more information, see the API reference.
[2]	Use the right base URL depending on which environment you want to get information from.
[3]	Use the traffic tile base URL for this request.

Note: The following example uses a HERE API Key for authentication. For the available authentication options, see the Identity & Access Management Developer Guide.

Tile requests must follow the pattern summarized by the following formula:

{Base URL}{Path}{resource (tile type)}/{map id}/{scheme}/{zoom}/{column}/{row}/{size}/{format}
?apiKey={YOUR_API_KEY}
&{param}={value}

Note: POST requests are not allowed.