APIHub
Back to Explore

HERE Network Positioning API v2

The HERE Network Positioning API v2 accepts radio network measurements (cellular and Wi‑Fi) through a POST /locate call and returns a geographic location estimate, optionally configurable with confidence level, fallback strategies, and additional data fields (e.g., altitude), while also providing simple health and version endpoints.

Geocoding
apiKeyQuery
HTTPS
CORS: Unknown
Description enriched
Visit official documentation

Latency

1021ms p95

Uptime

100.0% 30d

Playground

Verified

live

Endpoints

REST · JSON
GET

/health

Service health

POST

/locate

Location query

  • confidence (query) — Confidence level in percent for the accuracy/uncertainty in the location estimate response. 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 location estimate: the higher the number, the greater the confidence level).
  • Content-Encoding (header) — Indicates that the data in the body is gzip-encoded.
  • fallback (query) — Acceptable fallback options for cell and WLAN positioning. Values `area` and `any` apply to cell based positioning, and value `singleWifi` applies to WLAN based positioning. Both cell and WLAN options may be specified in the same request. If both `area` and `any` are specified, then `area` is ignored. By default, cell based positioning returns cell tower level location estimates only. If you allow a WGS-84 compliant geocoordinate location estimate based on LAC, RNC, TAC, NID, or RZ areas, use the `fallback=area` setting. If you use the `fallback=any` setting, the service uses all available cell fallback methods and therefore the location estimate in the response may be at the MNC, SID, or MCC level. For privacy reasons, the precise positioning based on a single WLAN AP is not possible. You can use the `fallback=singleWifi` setting to allow less accurate positioning based on a single WLAN AP. In that case, the center location of the position estimate will be deviated and the reported accuracy radius will be larger.
  • desired (query) — Comma-separated list of additional data fields that the service should include in the response if data is available. The query parameter supports the value `altitude`.
  • X-Request-ID (header) — ID used for correlating customer requests within HERE services. Used for logging and error reporting. Can be any string, but UUID is recommended. It will be echoed in the response.
  • required (query) — Comma-separated list of additional data fields that the service should include in the response. If the data is not available, the response contains an error message. The query parameter supports the value `altitude`.
GET

/version

API version

3 endpoints auto-detected

Authentication

This API uses an API key, passed as the "apiKey" query parameter. No OAuth required.

curl -X GET \
  "https://positioning.hereapi.com/v2/health?apiKey=YOUR_API_KEY"

positioning.hereapi.com · HTTPS only