Venue Maps API Developer's Guide

Requesting Signature

This is an example of how to request a signature. For the full reference, see Signature Service.

Using the Venue Maps API involves submitting signed requests against resources. The example below uses the placeholder text {YOUR_APP_CODE} and {YOUR_APP_ID} to indicate places where you should substitute your own unique app_id and app_code values. For more information about these authentication credentials, see Acquiring Credentials. The Signature Service returns credentials necessary to construct signed requests to Venue Maps API.

Table 1. Basic elements of request to Signature Service
Element Value/Example Description
Base

http://signature.venue.maps.api.here.com

http://signature.venue.maps.cit.api.here.com

Production environment

Customer Integration Testing environment

Service venues
Feature signature
Version v1 Version number of Venue Maps API
Application Id app_id={YOUR_APP_ID} Substitute with your unique Application Id
Application Code app_code={YOUR_APP_CODE} Substitute with your unique Application Code
JSONP static callback function (optional) cbfn=JSON.venues Substitute with desired static callback URL encoded

Request

http://signature.venue.maps.cit.api.here.com/venues/signature/v1
  ?app_id={YOUR_APP_ID}
  &app_code={YOUR_APP_CODE}

Response:

{"status":
  {"code":"200","message":"OK"},
  "Hostname":"ip-10-96-40-53.eu-west-1.compute.internal",
  "SignedQueryString":"?Policy\u003deyJTdGF0ZW1lbnQiOiBbeyJSZXNvdXJjZSI6Imh0dHAqOi8vc3RhdGljLSoudmVudWUubWFwcy5jaXQuYXBpLmhlcmUuY29tLyo~YXBwX2lkPURlbW9BcHBJZDAxMDgyMDEzR0FMJmFwcF9jb2RlPUFKS25Ydjg0ZmpyYjBLSUhhd1MwVGciLCJDb25kaXRpb24iOnsiRGF0ZUxlc3NUaGFuIjp7IkFXUzpFcG9jaFRpbWUiOjE0NTUyNzIxNDR9LCJJcEFkZHJlc3MiOnsiQVdTOlNvdXJjZUlwIjoiMC4wLjAuMC8wIn0sIkRhdGVHcmVhdGVyVGhhbiI6eyJBV1M6RXBvY2hUaW1lIjoxMzkyMjAwMTQ0fX19XX0_\u0026Signature\u003dCEM8ouuwEB50pHwdDgiEqCQeotCUGfz2l1EX~wkFx2FUeou~kCabtlvI5pA5CNSxpkfPriYMdmovctNtPEVebKeBTiMpq8cmVj-ljPkTsZPm-Bnlp8MVP3mWHgOtA0PiFjouXIvfCqbGpzXN0V3mrHk150-s5z6ApN0RdmnQPB5Ac3tHrF7K77Cr6FO841a6437Mul-JIyEivzB-0n03mAvXlQ2KtIej0Nukh3SOJ93Q4OTMrnto09oSXwZ1JMIFQR5LkFadvW3~a4a7w6nPyabJGIKh2OIt~MixLwBelb1362X6oyVgnVNtcqENI-szzDQDsvBFUQh-TsvQReivrw__\u0026Key-Pair-Id\u003dAPKAJYHWIIHIUVYKYWZA\u0026app_id\u003d{YOUR_APP_ID}\u0026app_code\u003d{YOUR_APP_CODE}",
  "Expires":"2016-02-12T10:15:44Z",
  "SignatureTokens"{

"app_id":"{YOUR_APP_ID}",
"app_code":"{YOUR_APP_CODE}",
    "Signature":"CEM8ouuwEB50pHwdDgiEqCQeotCUGfz2l1EX~wkFx2FUeou~kCabtlvI5pA5CNSxpkfPriYMdmovctNtPEVebKeBTiMpq8cmVj-ljPkTsZPm-Bnlp8MVP3mWHgOtA0PiFjouXIvfCqbGpzXN0V3mrHk150-s5z6ApN0RdmnQPB5Ac3tHrF7K77Cr6FO841a6437Mul-JIyEivzB-0n03mAvXlQ2KtIej0Nukh3SOJ93Q4OTMrnto09oSXwZ1JMIFQR5LkFadvW3~a4a7w6nPyabJGIKh2OIt~MixLwBelb1362X6oyVgnVNtcqENI-szzDQDsvBFUQh-TsvQReivrw__",
      "Policy":"eyJTdGF0ZW1lbnQiOiBbeyJSZXNvdXJjZSI6Imh0dHAqOi8vc3RhdGljLSoudmVudWUubWFwcy5jaXQuYXBpLmhlcmUuY29tLyo~YXBwX2lkPURlbW9BcHBJZDAxMDgyMDEzR0FMJmFwcF9jb2RlPUFKS25Ydjg0ZmpyYjBLSUhhd1MwVGciLCJDb25kaXRpb24iOnsiRGF0ZUxlc3NUaGFuIjp7IkFXUzpFcG9jaFRpbWUiOjE0NTUyNzIxNDR9LCJJcEFkZHJlc3MiOnsiQVdTOlNvdXJjZUlwIjoiMC4wLjAuMC8wIn0sIkRhdGVHcmVhdGVyVGhhbiI6eyJBV1M6RXBvY2hUaW1lIjoxMzkyMjAwMTQ0fX19XX0_",

"Key-Pair-Id":"APKAJYHWIIHIUVYKYWZA"
}}
Note:

app_id and app_code are authentication credentials. This document uses {YOUR_APP_CODE} and {YOUR_APP_ID} as placeholders for access and authorization credentials. Please replace these placeholders with your own unique application-specific credentials to access the API resources. For more information about the access and authorization credentials credentials, see Acquiring Credentials.