How to construct a request

📘
Note
HERE Network Positioning API v1 is in maintenance and is not actively developed. Use HERE Network Positioning API v2 to get the latest features and updates. To learn more, see the HERE Network Positioning API v2 Developer Guide.

A typical request to the Network Positioning API v1 includes the basic elements shown in the following table and, in addition, it may contain resource-specific parameters or data.

Element	Value/Example	Description
Base URL	`https://pos.ls.hereapi.com`	Production environment when you use an API Key or an authentication token. For the full authentication story, see the Identity & Access Management Developer Guide.
Legacy Base URL	`https://pos.api.here.com`	Production environment when you use an app_id/app_code pair. For more information, see the Identity & Access Management Developer Guide.
Path	`/positioning/v1/`
Resource	`locate`	HTTPS POST only, submit data in the body of the request
HTTP header field	`Content-Type: application/json`	Used in both requests and responses.
HTTP header field	`Content-Encoding: gzip`	Optional header, indicates gzip encoded request body content
Application Code - Legacy	`&app_code={YOUR_APP_CODE}`	Substitute your own unique `app_code`. For more information, see the Identity & Access Management Developer Guide.
Application Id - Legacy	`&app_id={YOUR_APP_ID}`	Substitute your own unique `app_id`. For more information, see the Identity & Access Management Developer Guide.
API Key	`&apiKey={YOUR_API_KEY}`	Substitute with your own unique `apiKey`. For more information, see the Identity & Access Management Developer Guide.
HTTP header field	`Authorization: Bearer {YOUR_TOKEN}`	Authentication token. Not used in case of app_id + app_code or apiKey authentication. For more information, see the Identity & Access Management Developer Guide.
Desired	`&desired=altitude` `&desired=altitude	floor`
Required	`&required=altitude` `&required=altitude	floor`
Fallback	`&fallback=any	area
Confidence	`&confidence=50`	Confidence level in percent for the horizontal accuracy and, if requested, altitude accuracy, in the response location. If not specified, the default is 68 (this corresponds to a 68% probability that the true position is within the accuracy/uncertainty radius of the position; the higher the number, the greater the confidence level). Valid range is [50..98]

Here is an example of locate request, which uses API Key authentication:

POST https://pos.ls.hereapi.com/positioning/v1/locate?apiKey={YOUR_API_KEY}

Make sure to include request content type in the HTTP headers:

Content-Type: application/json

Here is an example of locate request, which uses token authentication:

POST https://pos.ls.hereapi.com/positioning/v1/locate&desired=floor

Make sure to include the authentication token and request content type in the HTTP headers:

Authorization: Bearer {YOUR_TOKEN}
Content-Type: application/json

The POST body is as follows

{
  "wlan": [{
    "mac": "36:68:95:1A:36:93",
    "powrx": -74
  }, {
    "mac": "18:64:72:B7:BC:B2",
    "powrx": -75
  },{
    "mac": "18:64:72:B7:89:21",
    "powrx": -76
  },{
    "mac": "18:64:72:B7:BC:B1",
    "powrx": -77
  },{
    "mac": "18:64:72:B7:B1:63",
    "powrx": -79
  }]
}

📘
Note
This example uses a HERE API Key token to authenticate your request. For the available authentication options, see the Identity & Access Management Developer Guide.