Skip to content

For online shops

Fewer returned parcels: the customer chooses the correct address right at checkout. Adatka suggests the address while the customer types, and before dispatch it flags when the postal code does not belong to the address or the house number is not in our data.

Live examples

What goes wrong at checkout

Customers type their address in a hurry, often on a phone: without accents, abbreviated, with the postal code from memory. The order goes on to the courier with that address. If the postal code belongs to a different part of the settlement, or the house number does not exist, the parcel comes back, customer service makes phone calls, and the delivery costs money and time a second time.

What Adatka changes

At checkout: address autocomplete while typing

The address field calls the /suggest endpoint: after a few letters the customer chooses from the list.

The postal code, settlement and street go into the order in a standard spelling; it also suggests house numbers where the source contains them.

It recognises abbreviations (u., krt.), input without accents and common typos.

Before dispatch: batch address validation

You send the order addresses to the /clean endpoint, up to 1,000 rows per call.

For each row you get back the standardised address and the match level: house, street or settlement.

The response flags when the postal code entered does not belong to the address and when the house number is not in our data. We do not silently overwrite anything.

Four addresses from checkout — as entered and as returned

The responses come from the live service (20 October 2026); the addresses are made up, not customer data. Click any of them to try it in the live demo.

Live demo · Sources and licences

Data status: Magyar Posta — dataset of 21 September 2026 · KSH Gazetteer (Helységnévtár) — 2025 edition · OpenStreetMap — extract of 16 August 2026 · GeoNames — download of 16 August 2026 · National Election Office (Nemzeti Választási Iroda) — dataset of 16 January 2026

What you need to integrate

Two endpoints, a simple REST API with JSON responses.

It can be called from any system that can send an HTTP request and read JSON — no separate software library is needed.

We do not currently offer a ready-made plugin for any online shop platform. If you need one for your system, write to us: info@adatka.hu.

You can view the raw API response in the live demo with the “API response (JSON)” button; the details of the call are in the API documentation.

GET /suggest?q=nyiregyhaza+dozsa+gy+u+5&limit=5

→ { query, suggestions: [ { postal_code, settlement,
    street, house_number, admin{…}, geo{…},
    meta{ match_level, sources, … } } ] }

POST /clean
{ "records": [ "9022 gyor baross gabor ut 12",
               "pecs kiraly u 999" ] }

→ { results: [ { input, postal_code, settlement,
    street, house_number, …,
    meta{ match_level, postal_not_matched,
          house_not_found } } ] }

What we do not promise

  • Validation of floor, door and staircase: we return them in a separate field, but as there is no public source, we do not validate them.
  • House numbers everywhere: we suggest house numbers where the source used contains them; where it does not, the response is at street level and says so.
  • Official certification: Adatka is not an official address register — it compares publicly released, openly licensed sources and shows which of them it worked from.
  • Figures on returned parcels: only results that we have actually measured with an online shop will appear here — with the measurement method, the period and the online shop’s consent.

Access

The service is currently available free of charge as an invitation-only beta; there is no self-service registration yet. Request access and we will get in touch with you.

Prices