Here we record, with dates, what has changed in Adatka: in API responses, in the data sources, in the terms and on the website.
This page is a translation of the Hungarian original. If the two differ, the Hungarian text prevails.
Before you read
We write and correct the entries according to the Rules for honest communication: we do not rewrite a published entry (section 2).
· 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.
· 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.
· 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.
· 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”.
· 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.
· 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.
· 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.”
· 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.
· 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.
· 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).
· 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).
· 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).
· 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.
· 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.
· Website · No action required
The “For online shops” page uses live examples to show what Adatka offers at the checkout of an online shop.
· 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.
· 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).
· 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.
· 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).
· Terms · No action required
We published the Terms of service, the Privacy notice, the Cookie notice, the Legal notice and the Accessibility statement.
So that you can see what has changed and when — rather than first noticing it in your own system. If you have integrated the API, you can check here whether you need to do anything.
Every change of the following kinds since 23 October 2026, and the more important of the earlier ones:
It is not a contract, and it does not amend the Terms of service; we inform you of changes to the terms as set out in section 8 of the Terms of service, and the log does not replace this. Liability is governed by section 7 of the Terms of service.
A response from Adatka does not certify that an address is correct or exists, and if there is no match for an address, that does not prove that the address does not exist either (Terms of service, section 4). Do not build a process that takes a decision, such as blocking an order, solely on the basis of a response from Adatka; instead, leave room for a manual check.
It is not a description of the current state: an older entry describes the state of things as of its own date.
If you find an error, write to info@adatka.hu.
The log is also available as an Atom feed.