The state of public APIs| Submit an API

|API RANK| by Escape.tech

Benchmark and ranking of 5138+ public APIs by Escape.tech

Back to the list Request ranking update

HERE Network Positioning API v2 (ranked 531 of 5138)

https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/HERE_Network_Positioning_API_v2_21027130_7030_47c9_9076_902d45399fce_yaml.yaml

GENERAL INFORMATION

Positioning API accepts requests with radio network measurements and replies with corresponding location estimate. For more details and examples, see Developer's Guide. Cellular measurements are given in terms defined in 3GPP and 3GGP2 specifications, see the corresponsing documentation at http://www.3gpp.org.

Breaking changes from v1:

  • JSON fields
    altaccuracy, baselat, baselng, cellparams, pilotpower, pnoffset, powrx, rxlevel,
    have been deprecated and replaced with
    altAccuracy, baseLat, baseLng, cellParams, pilotPower, pnOffset, rss, rxLevel
    respectively.
  • Dependent parameters combined as a subobject.
    • CDMA, GSM, WCDMA, TD-SCDMA and LTE local identification parameters for serving cell moved under localId property.
    • GSM neighbor global ID: lac and cid for neighbor cell moved under globalIdentity property.

License

SECURITY 4/5

The security score of an API is computed as the number of OWASP top 10 vulnerabilities detected in the API.

  • OWASP issues detected: API7:2023

PERFORMANCE 4/5

The performance score is derived from the median response time of the API, sometimes referred as p50. The median is the value separating the higher half from the lower half of a data sample, here the response times of the API.

  • The median response time of the API is 125 ms .

Get p50 under 220 ms to get a 4/5 score.

RELIABILITY 5/5

The reliability score is derived from the number of inconsistent server responses, either server errors or non-conforming return values.

  • Self compliance: response objects matched the declared response types.
  • Server errors: the server did not return any 5xx error.

DESIGN 4/5

The design score reflects the quality of the specification file (usually named openapi.json or swagger.json). Having a high-quality specification file (with up-to-date types and examples) help developers understand the API and tools produce relevant documentation.

  • Respects OpenAPI 3.0.0 schema specification.
  • Contains comments and summaries.
  • Contains examples.
  • Does not contain duplicated objects.

Popularity 0/5

The popularity score is computed from the number of references to the API found on the internet. Have your API used by many developers to get a higher score!

Last scanned: 5/4/2023