Location & geocoding API — US, Australia & expanding

Production-ready APIs for every location workflow

Address autocomplete, geocoding, geofencing, routing, device tracking, and webhooks — ship location features without the complexity.

In your stack

Drop-in HTTP, not a maps widget

Call Wherabouts from your backend or edge with plain REST—no embedded map SDK required to validate an address, power autocomplete, or geocode a signup. US and Australia are at the core, with coverage expanding across Europe, South America, Africa, and Asia.

See what you get

From API key to first result in minutes

Install the SDK or call the same endpoints over plain HTTP. Pick an endpoint to see a real request.

GET /api/v1/addresses/autocomplete
import { createWheraboutsClient } from "@wherabouts/sdk";

const client = createWheraboutsClient({
  apiKey: process.env.WHERABOUTS_API_KEY!,
});

const result = await client.addresses.autocomplete({
  q: "123 Main",
  country: "AU",
  state: "VIC",
  limit: 10
});
console.log(result);
Example response
{
  "results": [
    { "id": 123, "label": "123 Collins St, Melbourne VIC 3000", "lat": -37.8159, "lng": 144.9669 }
  ]
}

Built for locations in production

Pricing you can plan around, APIs you can integrate quickly, and international coverage aimed at real app flows—not a generic maps platform bolt-on.

Testimonials

What teams are building with Wherabouts

Engineers and product teams shipping location features in production—autocomplete, geocoding, geofencing, and more.

PN

Priya Nair

Staff Engineer · Routora

We wired address autocomplete and checkout validation in an afternoon—plain HTTP from our API route, no embedded map SDK to ship.

DO

Daniel Okafor

Product Lead · Saveo

Geocoding our signups cut bad addresses to near zero. Clear errors meant we weren't guessing why a lookup failed between staging and production.

SA

Sofia Almeida

Co-founder & CTO · Parcela

From API key to a working geocode was minutes with the SDK. We spent our time on product logic, not console setup.

PN

Priya Nair

Staff Engineer · Routora

We wired address autocomplete and checkout validation in an afternoon—plain HTTP from our API route, no embedded map SDK to ship.

DO

Daniel Okafor

Product Lead · Saveo

Geocoding our signups cut bad addresses to near zero. Clear errors meant we weren't guessing why a lookup failed between staging and production.

SA

Sofia Almeida

Co-founder & CTO · Parcela

From API key to a working geocode was minutes with the SDK. We spent our time on product logic, not console setup.

PN

Priya Nair

Staff Engineer · Routora

We wired address autocomplete and checkout validation in an afternoon—plain HTTP from our API route, no embedded map SDK to ship.

DO

Daniel Okafor

Product Lead · Saveo

Geocoding our signups cut bad addresses to near zero. Clear errors meant we weren't guessing why a lookup failed between staging and production.

SA

Sofia Almeida

Co-founder & CTO · Parcela

From API key to a working geocode was minutes with the SDK. We spent our time on product logic, not console setup.

PN

Priya Nair

Staff Engineer · Routora

We wired address autocomplete and checkout validation in an afternoon—plain HTTP from our API route, no embedded map SDK to ship.

DO

Daniel Okafor

Product Lead · Saveo

Geocoding our signups cut bad addresses to near zero. Clear errors meant we weren't guessing why a lookup failed between staging and production.

SA

Sofia Almeida

Co-founder & CTO · Parcela

From API key to a working geocode was minutes with the SDK. We spent our time on product logic, not console setup.