Adatka — Development log

A known exception to the flags for single-word requests

2026-10-24T00:00:00Z

A known exception to the flags for single-word requests

24 October 2026 · API · Action required

The API documentation now also describes a currently known exception: if the request is a single word that is not exactly the name of a settlement, the response may return the most similar settlement or settlement part without a flag, with a confidence of 0.95 (see Match levels and flags). The way the service works has not changed, but the documentation did not mention this until now.

Action: for single-word requests, compare the word you entered with the settlement or settlement_part field.

Redirects from the www addresses and from adatka.org and adatka.net

2026-10-24T00:00:00Z

Redirects from the www addresses and from adatka.org and adatka.net

24 October 2026 · Website · No action required

From 23 October 2026, www.adatka.hu, www.adatka.com and www.adatka.eu redirect to adatka.hu; previously, browsers could not open them and showed an error instead. From 24 October 2026, adatka.org and adatka.net — with and without www — also redirect to adatka.hu.

The Accessibility statement was amended

2026-10-24T00:00:00Z

The Accessibility statement was amended

24 October 2026 · Terms · No action required

According to the Accessibility statement, every page within its scope now has an English version, and the statement does not apply to the /api-kulcs-ru/ page, which is in Russian (section 1); on the Development log and the “Rules for honest communication” page, too, the language switcher in the header now takes you to the version of the page in the other language (section 4), and we have added to section 6 the check of the English versions of these two pages and the check of the language switcher.

The Development log and the “Rules for honest communication” are now also available in English

2026-10-24T00:00:00Z

The Development log and the “Rules for honest communication” are now also available in English

24 October 2026 · Website · No action required

The Development log and the Rules for honest communication can now also be read in English; the language switcher in the header (EN) takes you to the English version of the page. We translated the earlier entries into English on 24 October 2026. The English version is a translation: if it differs from the Hungarian, the Hungarian text prevails. The English log also has its own Atom feed.

New “Contact” page; the header menu was restructured

2026-10-23T00:00:00Z

New “Contact” page; the header menu was restructured

23 October 2026 · Website · No action required

The “Contact” page shows where you can write with a question, an error report or a custom offer. The “Solutions” menu item has been removed from the header: the “For online shops” page and the “Who it is for” section of the home page can now be found in the “Use cases” column of the “Products” menu; the “API” menu item has been renamed “API documentation”.

The Accessibility statement was amended

2026-10-23T00:00:00Z

The Accessibility statement was amended

23 October 2026 · Terms · No action required

We extended the scope of the Accessibility statement to the Development log, the “Rules for honest communication” page and the “Contact” page; in section 4 we made the description of the language switcher more precise, and we added the check of these three pages to section 6.

The Development log and the “Rules for honest communication” page were published

2026-10-23T00:00:00Z

The Development log and the “Rules for honest communication” page were published

23 October 2026 · Website · No action required

In this log we record, with dates, what has changed in Adatka. The Rules for honest communication describe how we inform you; they cover dates, corrections, limitations, sources and links. We wrote the earlier entries retrospectively, when the log was published: they record the more important changes that have occurred since the website was launched and that we have verified.

New text on the Prices page

2026-10-22T00:00:00Z

New text on the Prices page

22 October 2026 · Website · No action required

The “Prices” page now reads: “We will not publish prices until we can see precisely how the service is used and can establish predictable pricing that stays stable over the longer term.”

Prices and data sources now have their own pages

2026-10-21T00:00:00Z

Prices and data sources now have their own pages

21 October 2026 · Website · No action required

“Prices” and “Data sources” used to be sections of the home page; now each can be read on its own page.

English version and dark appearance

2026-10-21T00:00:00Z

English version and dark appearance

21 October 2026 · Website · No action required

The website can also be read in English; the language and the light or dark appearance can be chosen in the header.

Step-by-step selection with a settlement part

2026-10-06T00:00:00Z

Step-by-step selection with a settlement part

6 October 2026 · API · No action required

New settlement_part parameter alongside settlement (see Step-by-step selection). For an address match, the settlement_part field only gets a value if the data show that the address belongs to the settlement part (see Address object).

Material change to the Terms of service: a numerical quota for use without a key

2026-10-05T00:00:00Z

Material change to the Terms of service: a numerical quota for use without a key

5 October 2026 · Terms · Action required

We published a material change to the Terms of service: from 5 November 2026, a numerical quota applies to use without a key (section 5); until then, the anti-abuse brake applies. The change is described in the new text of the Terms of service, and the figures are in the “Limits” section of the API documentation.

Action: if you call the API without a key and at high volume, request an API key (see the “Limits on use without a key” entry).

Settlement parts in the search

2026-10-05T00:00:00Z

Settlement parts in the search

5 October 2026 · API · No action required

The search recognises city quarters, housing estates and other settlement parts (for example “Békásmegyer”, “Jereván-lakótelep Sopron”). New match level: settlement_part; new flag: settlement_part_not_matched (see Match levels and flags). Sources: OpenStreetMap and the KSH Gazetteer (Helységnévtár).

Limits on use without a key

2026-10-05T00:00:00Z

Limits on use without a key

5 October 2026 · API · Action required

For use without a key, the service now restricts abusive requests, and from 5 November 2026 a numerical quota will also apply to this use. For calls without a key, the body of the 429 response states which limit is involved (see Limits).

Action: if you call the API without a key and at high volume, request an API key.

The API documentation was published

2026-10-04T00:00:00Z

The API documentation was published

4 October 2026 · Website · No action required

The API documentation was published in Hungarian: it describes the endpoints, the fields of the address object, the match levels, the error codes and the limits, with curl and Python examples.

New page for online shops

2026-10-04T00:00:00Z

New page for online shops

4 October 2026 · Website · No action required

The “For online shops” page uses live examples to show what Adatka offers at the checkout of an online shop.

We published the new text of the Terms of service and the Data processing terms

2026-10-03T00:00:00Z

We published the new text of the Terms of service and the Data processing terms

3 October 2026 · Terms · No action required

The new text of the Terms of service and the Data processing terms take effect on 2 November 2026. Until then, the current Terms of service remain in force.

New match level: the house number is known, but there are no coordinates for it

2026-09-28T00:00:00Z

New match level: the house number is known, but there are no coordinates for it

28 September 2026 · API · No action required

Source: Nemzeti Választási Iroda, Körzetállomány · Dataset: 16 January 2026

If the house number appears in the address dataset of the National Election Office (Nemzeti Választási Iroda), but we have no coordinates of our own for it, the value of match_level in the response is house_exists, and the meta.house_exists flag gives the source and the date of the extract. In such cases, the precision of the coordinates is shown by geo.precision (see Match levels and flags).

New flag: postal_alias — the postal_code field does not always contain the postal code entered

2026-09-23T00:00:00Z

New flag: postal_alias — the postal_code field does not always contain the postal code entered

23 September 2026 · API · No action required

If another source assigns the postal code entered to the settlement, but according to Magyar Posta the postal code of the settlement is a different one, the postal_code field of the response contains the postal code according to Magyar Posta, and the value entered is given in the meta.postal_alias flag (for example “csömend 8700” → postal_code: "8703", meta.postal_alias: "8700"; see Match levels and flags). Previously, the postal_code field contained the postal code entered even in such cases.

New data source: postal code and street data from Magyar Posta

2026-09-23T00:00:00Z

New data source: postal code and street data from Magyar Posta

23 September 2026 · Data · No action required

Source: Magyar Posta Partner Extra · Dataset: 21 September 2026

The search also uses the postal code and street data from the Magyar Posta Partner Extra dataset dated 21 September 2026. If this source also contributed to a match, Magyar Posta also appears in the list of sources in the response (meta.sources).

The legal pages were published

2026-09-20T00:00:00Z

The legal pages were published

20 September 2026 · Terms · No action required

We published the Terms of service, the Privacy notice, the Cookie notice, the Legal notice and the Accessibility statement.