News submission and NakBus fleet are now in the partner dashboard
Connect your developer account to a Nakordoni Partners account with the same email and manage news and your bus fleet (NakDriver / NakManager) there, with team roles. Your API keys, endpoints and apps are unchanged, and the pages here keep working. Open Nakordoni Partners
Live Border Queue API Online
Real-time queue length, wait estimate and status for any monitored checkpoint. Includes a snapshot block: current queue (queue_now), prognosed wait time wait_min, data age and source.
GET https://nakordoni.eu/api/v1/data/queue
— quota class: heavy
| Parameter | Description |
|---|---|
ppid | Checkpoint ID, e.g. id_13 (see /api/v1/data/checkpoints) |
section | Data section (optional) |
origin | Origin country code (optional) |
destination | Destination country code (optional) |
Response fields — inside the data object of the envelope. [] marks a list, so data.items[].name is the name field of each element. A field is null, absent or an empty list when we hold no value for it — never a placeholder.
| Field | Description |
|---|---|
data[] | Hourly series for the checkpoint, oldest first — one element per reading. |
data[].time | Unix timestamp of the reading, in the checkpoint's own timezone. |
data[].avg_cars | Vehicles in the queue at that hour. |
data[].wait_time | Wait in minutes at that hour. |
data[].wait_time_estimated | true = the wait is our estimate from the queue length, not an official figure. |
data[].type_of_data | 1 = a real observation; 2 = a forecast point (future hours). It says whether the row was measured or predicted — it carries no information about where the reading came from. |
data[].data_quality | How that row was arrived at: high = counted from a real observation source at the crossing, low = a modelled estimate where no counting source exists. Present on observation rows only (type_of_data 1) — a forecast point is predicted by definition. Same high|low vocabulary as the checkpoints directory, Border Queue and Best Time to Cross. Both are real answers; low is not an error, but it is an estimate and should be labelled as one if you show it to drivers. |
snapshot.timezone | IANA zone that snapshot.updated_at is expressed in — it is the checkpoint's own local time, not one fixed zone (e.g. Europe/Istanbul for id_385, Europe/Sofia for id_390, Europe/Budapest for id_407). Use it to resolve updated_at to an absolute instant. |
snapshot | Envelope-level, beside data: the current state — queue_now, wait_min, updated_at, timezone, age_min, data_quality. Read this for 'now'; data is the history behind it. |
curl "https://nakordoni.eu/api/v1/data/queue?ppid=id_13" \ -H "Authorization: Bearer NKD-DEV-XXXX-XXXX-XXXX"
🔑 Log in as a developer to try this endpoint live in the sandbox — 50 free test calls a day. Log in
Updated