Nachrichteneinreichung und NakBus-Flotte sind jetzt im Partner-Dashboard
Verknüpfen Sie Ihr Entwicklerkonto mit einem Nakordoni-Partners-Konto mit derselben E-Mail-Adresse und verwalten Sie dort Nachrichten sowie Ihre Busflotte (NakDriver / NakManager) mit Teamrollen. Ihre API-Schlüssel, Endpunkte und Apps bleiben unverändert, und die Seiten hier funktionieren weiterhin. Nakordoni Partners öffnen
API für das Grenzübergangs-Verzeichnis Online
Verzeichnis aller überwachten Grenzübergänge: IDs, Namen, Länder, Koordinaten und Status. Damit ermitteln Sie die ppid-Werte für die anderen APIs.
GET https://nakordoni.eu/api/v1/data/checkpoints
— Kontingentklasse: cheap
| Parameter | Beschreibung |
|---|---|
country | Filtern nach numerischem Ländercode (1=UA, 2=PL, 3=SK, 4=HU, 5=RO, 6=MD, 7=BY, 8=LT, 9=LV, …) |
lang | Sprache für Grenzübergangsnamen (Standard en) |
Antwortfelder — innerhalb des data-Objekts im Antwortumschlag. [] steht für eine Liste, data.items[].name ist also das Feld name jedes Elements. Ein Feld ist null, fehlt oder ist eine leere Liste, wenn wir keinen Wert dafür haben — nie ein Platzhalter.
| Feld | Beschreibung |
|---|---|
data.checkpoints[].ppid | Checkpoint ID — the value every other product's ppid parameter takes. |
data.checkpoints[].name | Checkpoint name in the requested language. |
data.checkpoints[].origin | Numeric country code of the side the crossing is operated from. |
data.checkpoints[].destination | Numeric country code of the country across the border. |
data.checkpoints[].crossing_type | Vehicle type this row is monitored for: 4=car, 5=taxfree car, 6=bus, 7=pedestrian, 8=truck (Freight Transport), 9=truck up to 7.5 t. |
data.checkpoints[].timezone | IANA timezone of the crossing — every timestamp for it is in this zone. |
data.checkpoints[].status | 1=open, 3=closed, 0=inactive. |
data.checkpoints[].redirect_to | Present only on a checkpoint that was RETIRED as a duplicate of another one at the same physical crossing: the ppid that superseded it. Such a row always carries status 0 — point your integration at the id named here. The retired id still answers the other products for now, but it is not the canonical one and is not guaranteed to keep updating. |
data.checkpoints[].has_day_stats | false means the Best Time to Cross product has no matrix for this checkpoint and would answer 404 — skip it rather than poll it. |
data.checkpoints[].has_live_data | Whether a live queue value currently exists for this checkpoint, i.e. whether the queue and border products will return a number for it rather than nothing. It says nothing about how recent that number is — read last_observation for that. About 65 of the monitored checkpoints have no live source at all. Absent from every row if the live-value store could not be read at all, so treat "key missing" as unknown, not as false. |
data.checkpoints[].last_observation | ISO 8601 timestamp of the live value behind has_live_data, or null when there is none. Some checkpoints keep answering with a value that stopped moving long ago — a few of them years ago — so check this age before presenting the queue as current. |
data.checkpoints[].data_quality | How the current live value was arrived at: high = counted from a real observation source at the crossing, low = a modelled estimate where no counting source exists. Same vocabulary as the Best Time to Cross and live queue products. Present only when has_live_data is true; omitted otherwise. Both are real answers — low is not an error — but a low value is an estimate and should be labelled as one if you show it to drivers. |
data.count | Number of checkpoints returned. |
curl "https://nakordoni.eu/api/v1/data/checkpoints" \ -H "Authorization: Bearer NKD-DEV-XXXX-XXXX-XXXX"
🔑 Melden Sie sich als Entwickler an, um diesen Endpunkt live in der Sandbox auszuprobieren — 50 kostenlose Testaufrufe pro Tag. Anmelden
Aktualisiert