Pricing
$0.44 per 1 000

Addresses in, coordinates out. And the other way round.

One endpoint for a doorstep in Lisbon and a rural plot in Manitoba, with a scoring block that tells you how much of the query actually matched — so you can reject a bad hit instead of shipping a parcel to the wrong street.

Free
30K
HERE list
$0.88
ApiNavi
$0.44
Endpoints
3

Scoring you can act on

Every result carries a query score and per-field scores. A house number that was inferred rather than matched is visible in the payload, which is what lets you gate on confidence instead of guessing.

Batch that does not time out

Submit up to 50 000 rows per job, get a callback when the result file is ready. Batch rows bill at the same rate as single calls — no premium for doing it properly.

Written the way people type

Missing postcodes, transposed house numbers, district names used as cities, mixed scripts. The parser is tuned on messy checkout input, not on clean postal files.

Try it now

Endpoints

The sandbox answers without a key. Response shapes are the documented ones.

curl -sG "https://api.apinavi.com/v1/geocode" \
  -H "Authorization: Bearer $APINAVI_KEY" \
  -d "q=Torstraße 66, Berlin" \
  -d "in=countryCode:DEU"
ResponseSandbox data

Parameters

EndpointParametersRequest
/v1/geocodeGETqTorstraße 66, Berlin
inrestrict the search spacecountryCode:DEU
langde
limit5
/v1/revgeocodeGETat52.5296,13.4030
typesaddress,street
langen
/v1/geocode/batchPOSTrowsup to 50 000 per job
callbackhttps://your.app/hooks/geocode
What this costs

All ten billed services

Free allowance first, then the ladder. HERE's published rate is shown struck through.

ServiceFree / monthHERE listApiNavi
Geocoding & searchAddress in, coordinates out — and back.30K$0.88$0.44
Places & autosuggestTypeahead and category browse over 250M places.30K$2.00$1.00

Limits that matter

  • 500 requests/second per key on Growth, higher on Scale
  • Batch jobs: 50 000 rows, results retained 7 days
  • Response languages: 40, falling back to the local name

Coming from HERE? The parameter map is one page away. Read the HERE migration guide

Questions

How close is this to HERE's geocoder response?

Field names and nesting match: items[].address.label, items[].position, items[].scoring.queryScore. The differences are documented in the migration guide — mostly that we return fewer result types for administrative areas.

Does reverse geocoding bill differently?

No. Forward, reverse and batch all draw from the same geocoding meter at $0.44 per 1 000 after the 30 000 free.