Venue Maps API Developer's Guide

Venue Maps API request

A request to the Venue Maps API includes the basic elements shown in the following table and, in addition, it may contain resource-specific parameters.

Table 1. Basic elements of request to Venue Maps API
Element Value/Example Description
Base URL

http://static-{1-4}.venue.maps.api.here.com

http://static-{1-4}.venue.maps.cit.api.here.com

Production environment

Customer Integration Testing environment

Access

0 or 1

Feature access parameter

Resource

tiles-png

tiles-ia

tiles-ia-b64

models-poi

models-full

GET only, specify request details via query parameters

Level L{n} n is the number value of the floor level which is requested for the venue. Only needed for tiles tiles-png , tiles-ia , tiles-ia-b64
Application Code app_code={YOUR_APP_CODE} Substitute your own unique Application Code
Application Id app_id={YOUR_APP_ID} Substitute your own unique Application Id
Signature Signature=<Signature-value> Substitute your unique Signature
Key-Pair-Id Key-Pair-Id=<Key-Pair-Id-value> Substitute your unique Key-Pair-Id
Policy Policy=<Policy-value> Substitute your unique Policy

Generic Requests

Generic request to a Venue Maps API tile looks as follows
<Base URL>/<Access>/<Resource>/<Level>/<quadkey>.<filename extension>?<Application Id>&<Application Code>&<Policy>&<Signature>&<Key-Pair-Id>
Generic request to a Venue Maps API model looks as follows
<Base URL>/<Access>/<Resource>/<Venue Identifier>.<filename extension>?<Application Id>&<Application Code>&<Policy>&<Signature>&<Key-Pair-Id>

Examples

Tile Example:

http://static-3.venue.maps.cit.api.here.com/0/tiles-png/L0/03022223103013033.png?
  Policy={YOUR_GENERATED_POLICY}
  &Signature={YOUR_GENERATED_SIGNATURE}
  &Key-Pair-Id={YOUR_GENERATED_KEY_PAIR_ID}
  &app_id={YOUR_APP_ID}
  &app_code={YOUR_APP_CODE}

Response:

For More Tile Examples, Please check Examples Section

Model Example:

http://static-3.venue.maps.cit.api.here.com/1/models-full/DM_7171.json?
  Policy={YOUR_GENERATED_POLICY}
  &Signature={YOUR_GENERATED_SIGNATURE}
  &Key-Pair-Id={YOUR_GENERATED_KEY_PAIR_ID}
  &app_id={YOUR_APP_ID}
  &app_code={YOUR_APP_CODE}

Response:

{"content":
  {"category":
    {
    "id":"shopping","nt":"6512"
    },
    
    "phoneNumber":"+49 (30) 2693400",
    "placeId":"",
    "names":{"GER":"Alexa Shopping Center"},
    "addresses":
      {"GER":{"postalCode":"10179",
      "countryCode":"DEU",
      "houseNumber":"20",
      "streetName":"Gruner strasse",
      "district":"DE","city":"Berlin"},
      "ENG":{"postalCode":"10179",
      "countryCode":"DEU",
      "houseNumber":"20",
      "streetName":"Gruner strasse",
      "district":"DE","city":"Berlin"}},
    "contentId":"814985"},
  
  "connectors":[{
    "destination2":"Lv15003Ds_2486040",
    "connectorClass":"ELEVATOR",
    "destination1":"Lv15004Ds_2486057"}, ... 
           == Content Truncated == 

For More Model Examples, Please check Examples Section

Note: There is an CDN service configured. The server pools are load balanced and the URLs are pointing to a CDN. It can be accessed using a suffix between 1 and 4. The different suffixes can be used to download the data parallel and in order to get the optimal cache hit rates, the URL prefixes 1, 2, 3 and 4 should be used for row and column numbers that are both even, even and odd, odd and even and both odd, respectively. The main application of this feature is to allow web browser clients to use domain sharding.