Pricing
Legal

Terms of service

Last updated: 27 July 2026

Written to be read. Where a clause has a practical consequence, the consequence is stated rather than implied.

What this covers

These terms govern access to the ApiNavi APIs, console and documentation. Accepting them happens by creating an account or sending an authenticated request, whichever comes first.

A separate order form may add terms for committed volume. Where it conflicts with this document, the order form wins for that customer only — and only where it is more favourable to you.

Where a clause below is more generous than the market default, the comparison page sets it against the vendor clause it answers, quoted and dated.

Your account and keys

You are responsible for keys issued to your account, including keys committed to a public repository. Rotation is available at any time from the console with a 24-hour overlap window.

One account may hold multiple keys with different service scopes. Sharing a key outside your organisation is a breach; reselling raw API responses as a competing location service is also a breach.

Billing, and what the price may do

Usage is metered per successful response. Requests that return 4xx validation errors or are rejected by a rate limit are not billed.

Free allowances reset on the first of each month in UTC and do not roll over. Paid usage is invoiced monthly in arrears in USD or EUR.

Your rate is fixed for the duration of any term you commit to. Outside a committed term, an increase takes effect only after 90 days' written notice, and you may end the agreement inside that window with unused prepaid volume refunded.

The half-of-list rule is a term of this agreement and not a claim on a marketing page: while this contract is in force, the published ApiNavi rate for a service will not exceed half of HERE Technologies' published rate for the equivalent service. If their published rate falls, ours follows within 30 days. The pricing page names the figures, their sources and the date each was read.

Metering, and the audit we do not have

We hold no right to audit you: not your records, not your premises, not your applications. The meter is the record. It is visible to you in the console request by request and exportable for as long as the account exists.

If the meter under-counts, the shortfall is ours to absorb. If it over-counts, tell us and the difference is refunded — no notice window, and no cap on how far back a genuine error is corrected.

Nothing here stops us from investigating abuse under the acceptable-use policy. That is about protecting the platform, not about counting your money again.

What you may keep

Results you request are yours to keep for as long as they are useful to you. There is no expiry on a response you paid for and no separate licence to renew for holding onto it.

That right survives the end of this agreement. When an account closes we ask for no deletion, no certificate of destruction and no inspection of your systems.

Two limits, and they are about scale rather than time: you may not use the API to assemble a substitute for the underlying map, address or place database, and you may not resell raw responses as a competing location service. Caching for performance, storing what your own users looked up, and keeping records for audit or compliance are all fine.

What we commit to

Availability targets and service credits are in the SLA, and credits are applied without you having to claim them. API stability is governed by the deprecation policy: twelve months of notice minimum, announced in the changelog with a Sunset header on affected endpoints.

We do not sell, rent or share your query data. What we process and why is set out in the privacy notice and the DPA.

Attribution

Attribution is required in one place only: where a rendered basemap is on screen. One line of text in the documented form, legible, anywhere on the map surface.

Geocoding, routing, matrix, isoline and search results carry no attribution requirement. Nothing in this agreement obliges you to tell your own customers which supplier you use.

Suspension

We contact you before suspending an account and give you a reasonable period to put it right. The exceptions are narrow: a live threat to the platform or to people's safety, and a binding legal order.

Non-payment gets 14 days' notice. A suspension we later find was ours to answer for is refunded for the period, and credited under the SLA as downtime.

Ending it, and leaving with your work

Close the account from the console whenever you like. There is no notice period, no renewal window to miss and no termination fee; prepaid volume you did not use is refunded rather than forfeited.

We will keep a migration guide pointing away from us — to HERE, Google and Mapbox — for as long as we sell this service, and export your usage and invoice history on request. Leaving costs nothing.

We may end the agreement on 90 days' notice, or immediately for activity that threatens the platform or breaches the acceptable-use policy.

Changing these terms, and assignment

The terms you accepted hold for the length of your term. Changes take effect at renewal, not before, and each version is published with a diff in the changelog.

If you do not want the new version, say so before renewal and the agreement ends on its existing terms with unused prepaid volume refunded. Continuing to send requests is not treated as agreement to anything you have not seen.

Either party may assign this agreement to an affiliate or to a party acquiring substantially all of its business. Any other transfer needs the other side's consent, which will not be unreasonably withheld.

Liability

Location data is an estimate of the world, not the world. Routes, addresses and traffic conditions can be wrong, and safety-critical use is your responsibility to validate.

Each side's aggregate liability is limited to the fees paid in the twenty-four months before the claim. Two carve-outs sit above that cap: a data-protection failure on our side is capped at three times that figure, and our duty to defend you against a claim that ApiNavi data infringes a third party's rights is not capped at all.

Nothing here limits liability for fraud, death or personal injury caused by negligence, or anything else that cannot be limited by law.

Law

These terms are governed by the laws of the Netherlands, with the courts of Amsterdam having exclusive jurisdiction. Consumer rights that cannot be waived are unaffected.

These are commercial terms, not legal advice. They were drafted to be read by the people who have to live with them; have your own counsel read them before you rely on them.

Questions about this document go to [email protected].