Эта страница пока доступна только на английском языке. Обязательной является английская версия (пункт 17.2); перевод будет добавлен.
These Developer API Terms (“API Terms”) govern access to and use of the Nakordoni.eu Developer API, the developer portal, the API keys we issue and the data returned by the API. They apply to every plan, including the free Explorer plan.
The API Terms supplement our Terms of Use and Privacy Policy. Payment, renewal and refund rules for paid plans are in section 8 of the Terms of Use and in the Refund Policy. If the API Terms and the Terms of Use conflict on a point about the API, the API Terms prevail. The API documentation forms part of the API Terms; where it sets a specific rule (for example the attribution snippet or a quota), that rule applies.
1.1. The API is provided by Nakordoni.eu, the service operated at the domains nakordoni.eu and nakordoni.dev (“we”, “us”); the operator is identified in section 17.8. A postal address is available on request through the contact page or privacy@nakordoni.eu. We may transfer the API Terms to a company that takes over the service, on notice under section 17.4.
1.2. You accept the API Terms when you tick the acceptance box at sign-up, when you accept a new version in your dashboard, and each time you use an API key. If you use the API on behalf of a company or other organisation, you confirm you are authorised to bind it, and “you” means that organisation.
1.3. You must be at least 18 years old and not barred from using the API under applicable law. Registration details must be accurate and kept up to date, including the website, the “page where the data is used” and the markets you declare.
1.4. The API is designed for use in the course of a trade, business or profession. Paid plans are sold only to businesses, organisations and professionals acting in that capacity; by buying a paid plan you confirm that you are not acting as a consumer. Consumers may use the free Explorer plan. Where you are a consumer, sections 14.3, 15, 16 and 17 apply only to the extent permitted by the consumer law of your country of residence, and nothing in the API Terms removes rights that law gives you.
nakordoni.eu/api/ that we document for developers, the MCP server, the sandbox and the history export. nakordoni.dev is an alternative address of the developer portal and redirects to nakordoni.eu; API calls are served from nakordoni.eu./developers/docs, including the attribution and data-licence sections.3.1. Subject to the API Terms, we grant you a limited, non-exclusive, non-transferable, non-sublicensable, revocable licence, for the term of your account, to:
3.2. That is the whole licence. Anything not listed in 3.1 — in particular the uses listed in section 4 — requires our prior written agreement (an individual commercial licence, see section 4.3).
3.3. You own your Application and your Derived Data. We own the API and the Data (section 12). Nothing in the API Terms transfers ownership either way.
3.4. The free Explorer plan is provided for evaluation, development, side projects and low-volume Applications, with delayed Data and the attribution duty in section 8. Where an Explorer account's use matches a paid tier, we may ask you to upgrade; if you have not done so within 30 days of our request, we may apply reduced limits to the account.
4.1. You may not, and may not let anyone else:
4.2. Attempting any of the above is a material breach (section 14).
4.3. Bulk or white-label feeds, resale, redistribution to other businesses, research datasets and any use outside section 3 can be licensed individually. Open a support ticket describing the use; a separate written agreement is required before such use starts.
5.1. Data describes border traffic as we observe or estimate it. It is compiled from public information published by national border authorities, from cameras, from road-traffic flow, from driver and Telegram-community reports, and from our own statistical and forecasting models. It is not an official statement by any authority.
5.2. Some values are modelled: where no counting source exists at a crossing, the API returns an estimate produced by our model. Such values are flagged where the Documentation says so. A flagged value is a real answer, not an error, but it is an estimate and must be shown as one (section 9).
5.3. Every live value carries the time of its last observation or update. How current Data is depends on the source behind each crossing and on your plan; the free Explorer plan serves a deliberately delayed snapshot. Data may be stale, missing, wrong or interrupted at any time, and sources may change or disappear.
5.4. Forecasts, statistics and “best time to cross” figures are predictions. Actual waiting times can differ substantially.
6.1. You may cache live Data for up to 24 hours from its updated_at time, and only to serve your own Application. Cached values must keep their original timestamp and quality flag.
6.2. Checkpoint directory data (identifiers, names, coordinates) may be cached for up to 30 days.
6.3. History obtained through the History export product may be kept for the purpose you declared when exporting it, under the conditions shown at export time.
6.4. When your account ends or a Key is revoked, delete all cached Data within 30 days and stop displaying it. You may keep Derived Data and internal aggregates that do not contain individual Data values (a value for a specific crossing at a specific time) and from which such values cannot be read back.
7.1. Your licence covers only the countries approved for your account. A Market is a country whose Data you use — the country in which the checkpoint, border or other object you request is located. Where your End Users are located does not by itself require a Market. Declare every country whose Data your Application queries or shows, at sign-up; you can change the list from your dashboard at any time, and a change puts the account back into review while the countries already approved stay usable. We review declared markets within 5 business days of sign-up or of a change. If we have not decided by then, your requested markets run on the full limits of your plan until we decide; if we later decline a market, we tell you and give you 14 days to stop using it.
7.2. Until an account has been reviewed for the first time, and during the review period in 7.1 (up to 5 business days), your Keys run on reduced limits: the lower of your plan’s allowance and half of the Starter allowance. Countries already approved for your account keep their full plan limits while a later change is reviewed. We may approve only some of the countries you requested; the approved list, not the requested one, is what the licence covers.
7.3. Some plans are offered only in selected regions. Querying or publishing Data for a country that is not an approved Market, or continuing to use a declined Market after the 14 days in 7.1, is a material breach.
7.4. We may filter API responses to the Markets approved for your account, so that Data for a country that is not approved, or that has been declined, is not returned. The 14 days in 7.1 concern only what you have already cached or displayed.
8.1. Applications on the free Explorer plan must show the attribution “Data by nakordoni.eu” as a visible, clickable HTML link to nakordoni.eu, in the form specified in the Documentation, next to or under every block of Data, on every page or screen where Data appears, in readable size and contrast and not hidden. You may qualify the link with rel attributes such as nofollow or sponsored; we ask, but do not require, that it stay indexable. Native apps follow the mobile rule in the Documentation.
8.2. Paid plans may omit the attribution link, but may not remove the timestamps and quality flags required by section 9.
8.3. You may use the names “nakordoni.eu” and “nakordoni.dev” only for the attribution and for truthful statements that your Application uses our API. You may not use our name, logo or design in a way that suggests we endorse, sponsor, partner with or operate your Application, and you may not register domains, app names or social accounts containing “nakordoni”.
8.4. We may verify attribution on the page you declared at sign-up and elsewhere. We may name your Application as an API user in a showcase; tell us in a ticket if you object.
9.1. Every Data value you show to End Users must be accompanied by its observation time or its age (for example “updated 14:32” or “23 min ago”), taken from the timestamp fields in the response, not from the time of your request.
9.2. You may not describe a value as “live”, “real-time” or “now” if it is older than the freshness the response reports, or if the response marks it as delayed or modelled. A value flagged as a modelled estimate must be labelled as an estimate.
9.3. You must not present Data as official information of any border authority, and you must give End Users a notice, in substance, that waiting times are estimates that can change without warning and that they should verify with official sources before relying on them.
9.4. You are responsible for your Application, its End Users and its compliance with the laws that apply to it, including consumer and privacy law.
9.5. Personal data. Send us only the personal data an endpoint asks for (for example the position, time and content of a driver report), collected on a lawful basis, and tell the persons concerned in your privacy notice that such reports are shared with nakordoni.eu. For that data you are the controller of your own collection, and we are a separate, independent controller that processes it for the purposes in our Privacy Policy (publishing queue information, operating and improving the service); we do not act as your processor. If your use case requires us to process personal data on your behalf, ask for a data-processing agreement through a support ticket before sending it. The API is designed not to return personal data of End Users or of other developers; where a product relays the text of public community reports, you must not use it to identify or profile individuals.
10.1. Keep Keys confidential. Call the API from your servers, not from browsers or apps distributed to the public. You are responsible for all use made with your Keys, authorised or not; revoke and re-issue a Key from the dashboard as soon as you suspect it is exposed.
10.2. We log and monitor API use (requests, volumes, IP addresses, products, response codes and the pages we verify) to run the service, meter plans and check compliance, as described in the Privacy Policy. You will not interfere with that monitoring.
10.3. Keep the website and the page where Data is used, as declared on your account, accurate and current. Before you show Data on a surface materially different from the one you declared — another domain, an app, a bot or an internal system — tell us through a support ticket so we can record it. Data shown on a surface you have not declared is outside the licence.
10.4. Audit. Where we reasonably suspect a breach, we may ask you for information about how and where Data is used, including request logs, screenshots or test access to the Application, and you will answer within 10 days. Not more than once in any 12 months, and on 14 days' notice, we or an independent auditor bound by confidentiality may verify your compliance with sections 4, 6, 7, 8 and 9; you will cooperate in good faith. We bear the cost of the audit unless it reveals a material breach, in which case you reimburse it.
10.5. Markers. Data served to your Keys may carry key-specific markers (for example variations in ordering, precision, timestamps or synthetic records) that do not affect its use inside your Application. The presence of your Keys' markers in a surface, feed, dataset or model that is not your registered Application is evidence that the Data came from your account, and you accept it as such unless you prove otherwise.
11.1. Quotas, rates and freshness follow the plan on your account as shown on the billing page. When a limit is reached, requests are refused until it resets; there is no automatic overage charge.
11.2. We may add fields, products and parameters at any time without notice. A change that could break an existing integration is released as a new version of the affected endpoint; the previous version stays available for at least 90 days (30 days for the free Explorer plan) after we announce its retirement by e-mail to the account address and in the Documentation, unless a legal, security or upstream-licensing reason requires faster action.
11.3. We may change, suspend or discontinue any product or the API as a whole. Paid plans get the notice in section 8.6 of the Terms of Use for price and limit changes.
11.4. Products, endpoints, fields and the MCP server that we label beta, preview, experimental or sandbox may change, be limited or be withdrawn at any time without the notice in 11.2 and carry no commitment of any kind. Sandbox responses are for testing and must not be shown to End Users as current Data.
12.1. The Data, the API, the Documentation and the collections of Data we serve are our property or that of our licensors, protected by copyright and by the sui generis database right (Directive 96/9/EC and the national laws implementing it). The licence in section 3 is your only right to extract or re-utilise Data; extraction or re-utilisation of a substantial part of our databases beyond that licence, repeated or systematic extraction of insubstantial parts, and any use listed in section 4 infringe those rights independently of any contractual claim.
12.2. Some Data is derived from third-party services (including national border-authority feeds, traffic-flow and weather providers and public road-operator data). We do not pass on their raw content, and you receive no rights in it. If a third-party source requires a notice, we will publish it in the Documentation and you must display it as instructed.
12.3. If you send us feedback or suggestions, we may use them without obligation.
13.1. Support is provided through the ticket system in your dashboard, on a reasonable-effort basis. The API is provided without any availability, response-time or freshness commitment; planned maintenance is announced where practical. Status and freshness indicators in responses and headers are the reference for what you received.
13.2. Service credits. For paid plans we target a monthly availability of the API of 99.5%, measured on our side as the share of minutes in a calendar month in which we received requests and the documented endpoints answered valid requests with non-5xx responses; minutes in which no developer sent a request are not counted. If availability falls below the target in a month, you may claim, within 30 days after that month, a credit of 10% of that month's plan fee, applied to your next invoice. The credit is your sole remedy for unavailability. It does not apply to maintenance announced in advance, to events outside our control (section 17.7), to upstream source outages that affect Data freshness rather than API availability, or to suspensions under section 14, and it is not paid out in cash.
14.1. You may stop using the API at any time and delete your account from the dashboard.
14.2. We may suspend a Key or an account, on any plan, with immediate effect where: (a) we reasonably believe there is a breach of section 4, 7, 8 or 9; (b) the account, Key or Application creates a security, legal or upstream-licensing risk for us; (c) a payment is more than 14 days overdue; or (d) we are required to by law. For a first, minor attribution or labelling problem we send a reminder first and give at least 7 days to fix it. When we suspend, we tell you the reason and what is needed to lift the suspension, at the time or as soon as security allows, and we lift it once the cause is fixed. If a suspension turns out to have been unjustified, we lift it and, for a paid plan, extend your plan period by the time lost.
14.3. We may terminate the account for a material or repeated breach. We may also terminate the account without giving a reason with 30 days' notice by e-mail; in that case, for a paid plan, we refund the part of any prepaid fee that covers the period after termination. Termination for breach gives no right to a refund (section 8.7 of the Terms of Use); other refund rules are in the Refund Policy.
14.4. On termination or suspension you must stop using the API and Data, delete cached Data as set out in section 6.4 and remove Data from any public surface. Sections 4, 5, 6.4, 8.3, 9, 10.4, 10.5, 12, 14.4, 15, 16 and 17 survive termination.
14.5. We may keep a hashed record of an account terminated for abuse to prevent re-registration, as described in the Privacy Policy.
15.1. The API and the Data are provided “as is” and “as available”. To the extent permitted by law we exclude all warranties, express or implied, including any warranty of accuracy, completeness, timeliness, merchantability, fitness for a particular purpose or non-infringement. We do not warrant that the API will be uninterrupted, error-free or that Data will match conditions at the border at any moment.
15.2. To the extent permitted by law, we are not liable for indirect, consequential, special, exemplary or punitive damages, or for lost profits, revenue, business, goodwill or data, or for decisions taken in reliance on Data (including missed crossings, delays, fines, cargo loss or route changes), even if we were told they were possible.
15.3. To the extent permitted by law, our total liability for all claims arising out of or relating to the API Terms in any 12-month period is limited to the fees you paid us for the API in the 12 months before the event giving rise to the claim, or EUR 100 if that is greater.
15.4. Nothing in the API Terms limits liability for death or personal injury caused by negligence, for fraud, for wilful misconduct or gross negligence where it cannot be limited, or any other liability that cannot be excluded by law. If you are a consumer, your statutory rights are unaffected.
15.5. Unless prohibited by law, you will defend and indemnify us, our affiliates, contractors and licensors against any third-party claim, damage, fine and reasonable legal cost arising from your Application, your End Users, your breach of the API Terms or your use of Data in violation of law.
15.6. Your liability; contractual penalty. The limits in 15.2 and 15.3 apply to our liability only; they do not limit your liability for a breach of sections 4, 7, 8, 10 or 12 or for misuse of Keys. For each breach of section 4.1(a), (b), (c) or (h) you will pay us a contractual penalty (kara umowna) of EUR 5,000 or ten times the fees paid by you in the 12 months before the breach, whichever is higher, without prejudice to our right to claim damages exceeding the penalty and to injunctive relief. A continuing breach counts as a new breach for each started month after our written notice.
16.1. We may change the API Terms. Material changes are announced at least 30 days before they take effect, by e-mail to the account address and in the developer dashboard; changes required by law or by an upstream data licence, and changes that only add a new product or feature without narrowing your existing rights, may take effect immediately. If a change is to your detriment and you object before it takes effect, you may terminate the account and, for a paid plan, we refund the part of any prepaid fee that covers the period after the change. The version and effective date are shown at the top of this page, and previous versions are available on request.
16.2. Continued use of the API after the effective date is acceptance of the new version. We may also ask you to accept the new version in the dashboard before further use. If you do not agree, stop using the API and, for a paid plan, cancel before the next renewal.
17.1. Governing law and courts. The API Terms are governed by the law of Poland. Disputes are brought before the courts competent for our seat, except that a consumer may also sue and be sued in the courts of their country of residence, and any mandatory consumer protection of that country continues to apply.
17.2. Language. The English version of the API Terms is the binding one; translations are provided for convenience.
17.3. Notices. We send notices to the e-mail address on your account and through the dashboard; you send notices to us through a support ticket, the contact page or by e-mail to privacy@nakordoni.eu. Keep your e-mail address current.
17.4. Assignment. You may not transfer your account, Keys or the API Terms without our consent. We may assign the API Terms to a successor of the service on notice.
17.5. Entire agreement; severability; waiver. The API Terms, the Documentation, the Terms of Use, the Privacy Policy, the Refund Policy and any individual written agreement are the whole agreement about the API and replace earlier statements. If a provision is invalid, the rest remains in force. Not enforcing a provision is not a waiver.
17.6. Version. API Terms v1.1, published on 2026-09-06 and effective from 2026-10-06 (30 days after publication). It replaces v1.0 of 2026-09-05 before that version took effect. You do not need to do anything to accept this version. Continuing to use the API on or after the effective date constitutes your acceptance of it, and we record that acceptance against your account when you do. The current version is available in the dashboard at any time. If you do not wish to accept it, stop using the API before the effective date; you may close your account from the dashboard.
17.7. Events outside our control. We are not in breach of the API Terms and not liable for any failure or delay caused by events beyond our reasonable control, including outages, changes or withdrawal of national border-authority, traffic, weather or other upstream sources, hosting, network or power failures, cyber-attacks, government action, war, strikes or natural disasters. Section 13.2 sets out what, if anything, you can claim for unavailability.
17.8. Service provider. The API and the developer portal are operated by Andrii Kurhanskyi, trading as nakordoni.eu and nakordoni.dev. A postal address is available on request through the contact page or by e-mail to privacy@nakordoni.eu.
Questions? Open a support ticket in your dashboard or contact us at /en/contactus.