Example
Flag: the 1051 you entered does not belong to this address. We flag the discrepancy; we do not silently overwrite it.
What it standardises
Splits them into fields and returns them with accents and the full street type. Adds the postal code, county and coordinates where the source contains them.
“hegedus gyula u” becomes Hegedűs Gyula utca — including the double acute accent (ű).
The abbreviations “bp”, “ker” and “u” are expanded to their full, standard form.
If the postal code entered does not fit the street, we say so on a separate line. A silent correction is worse than the error: the person using the data does not know about it.
How to call it
A simple REST API with JSON responses. A uniform address object on every endpoint.
The details of the call — parameters, fields, error codes and examples — are in the API documentation. You can also view the raw response in the live demo with the “API response (JSON)” button.
→ { query, suggestions: [ { settlement, street,
house_number, postal_code, admin{ city_district },
meta{ match_level } } ] }
In development
- bulk processing of existing datasets;
- structural validation of personal names;
- format validation of email addresses and detection of common domain typos.
These functions are not currently part of the live service; the exception is batch address validation in the API (/clean, up to 1,000 rows per call).