Build bounded place search.

ApiPoi is in private pre-launch testing. Coverage, source rights and commercial terms are still under review. Data sources, licence documents and review status.

Two clear plans

Paid API Read + Write
Free API Write only

“Write” always means isolated quarantine intake. Every external submission is AI screened, then human verified before it can reach the live POI dataset.

Accept your developer invitation

Your invitation creates a submission-only account. Retrieval access and billing are separate.

Invited emailChoose a passwordConfirm password

Confirm developer email

Confirm your email, then sign in with your password. This does not grant paid access.

Create developer account

EmailPassword

Sign in

EmailPassword

API keys

Create an API key

Choose an application name and expiry. Your account plan determines key permissions.

Application name

Your API keys

Current plan

Usage

Metered retrievals and returned records, in UTC. Failed requests and write submissions are not part of this ledger.

Reporting period

Daily usage

By application

Recent access passes

Billing contact

Save your billing details ahead of launch. Saving does not purchase a plan or activate billing.

Payments & invoices

Payments are pending. Pricing remains provisional until our pre-launch review.

Checkout, invoices and payment methods are not connected yet. No charges can be made from this portal.

Account profile

Email
Account ID
Email verification: Verified

Your account email identifies the owner of your API keys.

Your details

Session security

Use Sign out when you finish on a shared device. Each application key can be revoked separately from the API keys page.

Start with your backend

Store each application key in your backend secret manager. Never put it in browser JavaScript, a mobile bundle, a URL or a screenshot.

Read the draft OpenAPI contract Download the backend example

The example requires a verified, read-enabled account, an unexpired key and an active access pass. It can consume up to five returned records when you run it.

Search and usage

GET /v1/partner/places/nearby requires latitude and longitude. Radius: 50–20,000 metres; up to 50 results. Keep each search within the area your user selected.

Every returned place consumes one record, including cache hits. Multiple keys share the account allowance. A refreshed cache does not mean the underlying source data was updated.

POST /v1/partner/contributions is separate, quarantined intake for review. Third-party submission and photo services are not generally available in this private preview.

Handle failures safely

401: missing, expired or revoked key. 402: read access or pass unavailable. 429: slow down before retrying. 500/503: service unavailable.

Do not retry authentication or quota failures repeatedly. A timed-out read may already have consumed records; check usage before retrying. Revoke a compromised key from API keys.

Payments stay pending and prices remain provisional. Catalogue/field lineage and release-specific licence applicability remain launch gates.

Data sources and licence notices