Highlights come back with the result
Character offsets for what matched, in the title and in the address. Your input field renders the bold parts correctly without a fuzzy match in the browser.
Autosuggest ranked by distance and query strength, with highlight offsets so the matched substring can be bolded without re-implementing the matching logic on the client.
Character offsets for what matched, in the title and in the address. Your input field renders the bold parts correctly without a fuzzy match in the browser.
EV charging with connector types and live availability, fuel with prices where licensed, parking, pharmacies, ATMs. Filter by category and radius, sort by distance.
Place ids survive data refreshes, so a saved favourite still resolves next quarter.
The sandbox answers without a key. Response shapes are the documented ones.
curl -sG "https://api.apinavi.com/v1/autosuggest" \
-H "Authorization: Bearer $APINAVI_KEY" \
-d "q=torstr" \
-d "at=52.5296,13.4030"| Endpoint | Parameters | Request |
|---|---|---|
| /v1/autosuggestGET | q | torstr |
| at | 52.5296,13.4030 | |
| limit | 8 | |
| /v1/browseGET | at | 40.4168,-3.7038 |
| categories1 200+ categories | ev-charging,fuel | |
| radius | 3000 | |
| /v1/lookupGET | id | here:pds:place:276u33db-... |
Free allowance first, then the ladder. HERE's published rate is shown struck through.
| Service | Free / month | HERE list | ApiNavi |
|---|---|---|---|
| Places & autosuggestTypeahead and category browse over 250M places. | 30K | $2.00 | $1.00 |
| Geocoding & searchAddress in, coordinates out — and back. | 30K | $0.88 | $0.44 |
Coming from HERE? The parameter map is one page away. Read the HERE migration guide
Yes, each autosuggest request is a transaction — as it is on every provider. Debouncing at 150 ms typically cuts the count by two thirds; the docs show the pattern.
Operator feeds, refreshed every 2–5 minutes depending on the network. Networks without a live feed return connector counts but no availability, and the payload says which is which.