GuidesKB Articles
Guides
  1. Getting Started

Is 404 reponse from Network Positioning API counted as valid transaction?

Short answer:
Yes, this is a valid API transaction, even though it failed with 404 or E606404.

The sample Network Positioning API request is:

POST https://positioning.hereapi.com/v2/locate?apiKey=...

Depending on what the payload is, the response could be:

{
  "title": "Not Found",
  "status": 404,
  "code": "E606404",
  "action": "The values provided in the request cannot produce any content ..."
}



This is exactly how the Network Positioning API to behave when no position can be computed from the provided radio measurements.

Endpoint & method are correct

  • Endpoint: https://positioning.hereapi.com/v2/locate
  • Method: POST
  • Authentication: API key in query parameter

Request was accepted and processed



If it were not a valid transaction, you would instead see errors like:

  • 401 Unauthorized (invalid/expired API key)
  • 403 Forbidden
  • 400 Bad Request (malformed JSON or missing required fields)

    None of those occurred.

404 is a data-level failure, not a request-level failure.

According to HERE documentation and real-world examples:

> E606404 – Position not found
> The provided cell/WLAN measurements are valid in format but cannot be resolved to a known location, or are too sparse / inconsistent.

Typical causes:

  • Cell IDs or WLANs are not in HERE’s coverage database
  • Measurements are too widely scattered
  • Only a single cell without fallback enabled
  • NB‑IoT / sparse LTE data (very common)

    From a HERE platform billing and transaction semantics perspective:

  • Request counts as a transaction
  • Authentication succeeded
  • Service logic executed
  • No location result could be produced

    This type of request is considered billable usage.
    Because the service attempted positioning and returned a structured API response (not an auth or validation error).

    The error message itself hints at next steps to improve the request success rate:

  • Add fallback parameters: fallback=area fallback=any fallback=singleWifi
  • Ensure cell/WLAN measurements are:
    + recent
    + consistent
    + from supported technologies

    These recommendations are explicitly documented by HERE

Final conclusion

Yes, the API query in the screenshot is a valid transaction
It failed because positioning data could not be resolved, not because the request was invalid

Reference:

Tags:

Positioning API, Network Positioning, E606404, 404 Error, Valid Transaction, Position Not Found, API Billing