HTTP Request Headers
The Map Feedback API uses HTTP Request Headers for authentication credentials and content settings for requests.
The following section explains each of the headers in detail.
Header Name | Description |
---|---|
Accept | Specifies which media types are acceptable for the response (see Accept header specification ).
|
Accept-Charset | Sets the character set used in the response. Default: UTF-8 . |
Auth-Service-Id | Specifies the application associated with the Map Feedback API. If you are using the Map Feedback API with another application, consult your HERE customer representative for the appropriate value. |
Auth-Identifier | Header to put in the fixed string "apikey", if you want to choose the apikey authentication mechanism. If you want to do use the deprecated app_id/app_code authentication, you need to put in here your own app_id . |
Auth-Secret | Header to put in your own apikey in case you want to choose the apikey authentication mechanism. If you want to do use the deprecated app_id/app_code authentication, you need to put in here your own app_code . |
Content-Type | Specifies the media type of the body in POST requests. Must be: |
Content Disposition | For new feedback submission requests: form-data; name=-"file";filename="myFile.png" For submitting an attachment for existing feedback: multipart/form-data, boundary="RANDOM_DELIMITER" |
http://host/path?CORSH=encodeURIComponent(JSON.stringify( {
"Content-Type": "application/vnd.here.layerObjectList+json; charset=utf-8",
"Accept": "application/json; charset=UTF-8",
"GroupId": "FGx1AWaAzKOo0imNkLmf",
"AuthServiceId": "here_app",
"Auth-Identifier": "<put your app id here>",
"Auth-Secret": "<put your app code/token here>"
} ) )