Skip to content

Meridian

Place autocomplete API for administrative regions — realtime, ranked, hierarchy intact.

Type ahead and get ranked location suggestions as you type — with parents, children, and region type in the same response, ready for production place pickers.

Product

Built for realtime autocomplete that still understands structure

Meridian is a place autocomplete API for administrative regions. As users type, the API returns ranked suggestions with the context your UI needs: district, municipality, parish, and the nested regions underneath.

Debounced client requests hit a prefix search index, so suggestions stay responsive while subtitles and child regions keep results unambiguous — without maintaining your own gazetteer or wrapping a general geocoder for typeahead.

Live demo

Try realtime autocomplete

Start typing an administrative region. Suggestions update in realtime as you type, with ranked matches, a regional subtitle, and child regions when a district or municipality has sub-areas.

Choose a country above to search its administrative regions. We keep adding new countries — see coverage.

Coverage

Countries the API will cover

Meridian is building administrative-region search across Europe and North America. The countries below are on the coverage roadmap for the same API.

Europe

  • Albania
  • Andorra
  • Austria
  • Azores
  • Belarus
  • Belgium
  • Bosnia-Herzegovina
  • Bulgaria
  • Croatia
  • Cyprus
  • Czech Republic
  • Denmark
  • Estonia
  • Faroe Islands
  • Finland
  • France
  • Georgia
  • Germany
  • Greece
  • Guernsey and Jersey
  • Hungary
  • Iceland
  • Ireland and Northern Ireland
  • Isle of Man
  • Italy
  • Kosovo
  • Latvia
  • Liechtenstein
  • Lithuania
  • Luxembourg
  • Macedonia
  • Malta
  • Moldova
  • Monaco
  • Montenegro
  • Netherlands
  • Norway
  • Poland
  • Portugal
  • Romania
  • Russian Federation
  • Serbia
  • Slovakia
  • Slovenia
  • Spain
  • Sweden
  • Switzerland
  • Turkey
  • Ukraine (with Crimea)
  • United Kingdom

North America

  • Canada
  • Greenland
  • Mexico
  • United States of America

Capabilities

What realtime autocomplete gets from Meridian

Every keystroke-driven request returns UI-ready fields: ranked titles, disambiguating context, and hierarchy when you need to expand or filter.

Realtime suggestions

Prefix search over normalized names responds as the user types. Debounce on the client, keep the API simple — each call returns the current top matches for the partial query.

Ranked relevance

Matches are scored with place importance so major regions appear before obscure names, which keeps autocomplete lists useful under short prefixes.

Administrative context

Each hit returns region type separately from the geographic subtitle, so shared names stay distinguishable across districts.

Child regions

Districts and municipalities include their nested sub-regions as structured children for nested navigation and scoped filtering.

Geographic containment

Parent and child links reflect real geographic containment rather than fragile name matching.

Country-aware indexes

Search is scoped by language and country index, keeping results relevant when the same API serves multiple markets.

UI-ready fields

Title and subtitle are already formatted for autocomplete rows. Postcodes are stripped from display strings to keep suggestions clean.

How it works

From raw place data to a search index

Meridian is a pipeline as much as an API. Place regions are extracted, enriched, linked, and indexed so realtime autocomplete stays fast under typing load.

  1. 01 — Extract

    Load place regions

    Region records and tags are imported, including names, admin levels, and region types used for display and filtering.

  2. 02 — Hierarchy

    Link parents and children

    Each place is linked to its containing regions and nested sub-regions, so autocomplete can surface hierarchy without extra client-side lookup.

  3. 03 — Enrich

    Add display names

    Human-readable display names and importance scores are attached, then normalized for accent-insensitive search.

  4. 04 — Serve

    Index for fast search

    Documents are indexed for prefix search. As users type, the API aggregates matches, loads full documents, and formats autocomplete fields for the client.

Use cases

Where Meridian fits in a product

Realtime place pickers

Power address and area autocomplete so users select a parish, municipality, or district with clear subtitles while suggestions update as they type.

Regional coverage tools

Delivery, insurance, and field-service products can search a parent region in realtime, then browse child regions without inventing their own administrative tree.

Internal ops search

Support and ops teams get instant place suggestions, then expand into contained municipalities or parishes for routing and assignment.

API surface

Realtime autocomplete, hierarchy included.

Call GET /locations/search on each debounced keystroke. Optional lang selects the country index, and limit caps how many ranked suggestions come back. Full parameter notes are in the API docs.

q

Partial text from the autocomplete input. Prefix matching starts after two characters.

lang

Country index code. us for the United States, nl for the Netherlands, de for Germany.

limit

Maximum results, from 1 to 100. The demo requests 10.

GET /locations/search?q=bretagne&lang=fr&limit=10

{
  "query": "bretagne",
  "language": "fr",
  "total": 1099,
  "results": [
    {
      "score": 8,
      "weighted_score": 3.96919786624,
      "display_name": "Bretagne, France métropolitaine, France",
      "title": "Bretagne",
      "subtitle": "France métropolitaine, France",
      "hierarchy_subtitle": "France métropolitaine, France",
      "display_name_norm": "bretagne, france metropolitaine, france",
      "location": {
        "id": 102740,
        "name": "Bretagne",
        "name_norm": "bretagne",
        "tags": {
          "name": "Bretagne",
          "name:en": "Brittany",
          "population": "3354854",
          "population:date": "2019"
        },
        "details": {
          "addresstype": "state",
          "name": "Bretagne",
          "display_name": "Bretagne, France métropolitaine, France",
          "display_name_norm": "bretagne, france metropolitaine, france",
          "address": {
            "state": "Bretagne",
            "ISO3166-2-lvl4": "FR-BRE",
            "region": "France métropolitaine",
            "country": "France",
            "country_code": "fr"
          }
        },
        "parent_id": 1403916,
        "ancestor_ids": [1403916, 2202162],
        "child_ids": [7398, 102430, 7465, 7447],
        "parents": [
          {
            "id": 1403916,
            "name": "France métropolitaine",
            "name_norm": "france metropolitaine",
            "region_type": "territorial"
          },
          {
            "id": 2202162,
            "name": "France",
            "name_norm": "france",
            "region_type": "territorial"
          }
        ],
        "children": [
          {
            "id": 7398,
            "name": "Côtes-d'Armor",
            "name_norm": "cotes-darmor",
            "region_type": "departement"
          },
          {
            "id": 102430,
            "name": "Finistère",
            "name_norm": "finistere",
            "region_type": "departement"
          }
        ],
        "lineage": "/2202162/1403916/102740/"
      }
    }
  ]
}

Each hit includes ranked autocomplete fields plus the full stored location document — parents, children, lineage, and address details — when clients need more than the suggestion row. Child lists are abbreviated in this example.

Pricing

Simple monthly plans. Unlimited calls.

Pick one country or every country on the coverage roadmap. Both plans include unlimited autocomplete requests — no per-call metering.

One country

Unlimited calls against a single country index.

€4 / month

  • Unlimited API calls
  • One country index of your choice
  • Ranked suggestions with parents and children

All coverage

All countries

Unlimited calls across every country Meridian covers.

€10 / month

  • Unlimited API calls
  • Every country on the coverage roadmap
  • Switch country per request with lang

FAQ

Administrative region search, answered

What is an administrative region autocomplete API?
It is a location search API that returns ranked place suggestions as a user types — districts, municipalities, parishes, and other administrative regions — including parent and child hierarchy in the same response.
How is Meridian different from a geocoding API?
Geocoders resolve addresses to coordinates. Meridian is built for typeahead over administrative regions: prefix matching, ranked relevance, region type, and nested children so product UIs can show unambiguous autocomplete rows without maintaining your own place database.
Which countries does the place autocomplete API cover?
Meridian indexes administrative regions across Europe and North America. Search is scoped by country. The live demo currently includes the United States, the Netherlands, Germany, Switzerland, France, Italy, Portugal, Spain, and the United Kingdom, with more countries on the coverage roadmap.
How much does unlimited autocomplete cost?
One country is €4 per month for unlimited API calls. All countries on the coverage roadmap are €10 per month, also unlimited. There is no per-request metering.
Does the API return hierarchy with each suggestion?
Yes. Each hit includes formatted title and subtitle plus the stored location document: parents, children, lineage, region type, and address details when the client needs more than the suggestion row.
Is Meridian a Google Places Autocomplete alternative?
Meridian is built for administrative regions (states, counties, municipalities, parishes), not street addresses or businesses. If your picker needs hierarchy over places rather than Google’s POI autocomplete, Meridian is the closer fit — country-scoped indexes and unlimited calls on a flat monthly plan.

Contact

Ready to ship place search that feels instantaneous?

Tell us about your product, coverage needs, or integration timeline. We will follow up with next steps.