API o'zgarishlar jurnali

The Multi-Checkpoint API (/api/v1/data/multi) now bills quota at ⌈(N PPIDs × sub-products) / 2⌉ — half the cost of equivalent individual calls. A request for 10 checkpoints with both sub-products now costs 10 units instead of 20. The X-Devapi-Units header and meta.units_consumed in the response reflect the discounted amount.

Fetch live queue status and data freshness for up to 20 checkpoints in a single API call — designed for dashboard builders who currently poll many PPIDs in a loop.

Quota counts fairly as N PPIDs × sub-products requested, so the total usage is identical to individual calls — but with one round-trip instead of many. GreenTravel-style patterns drop from 24+ calls/hour to 2.

GET /api/v1/data/multi?ppids=id_2,id_13,id_15,id_59&include=queue,update-info&lang=en

• include=queue — current queue_now, estimated wait_min, data age and checkpoint name
• include=update-info — data freshness, source classification, age in seconds/minutes
• Max 20 PPIDs per request; combine both sub-products in a single call for full dashboard data
• Response includes meta.units_consumed so you can track quota usage precisely

The queue product response now includes a top-level snapshot object with the latest real-time data and a computed prognosed wait time — the same formula used on the nakordoni.eu hero section:

snapshot.queue_now  — current cars in queue
snapshot.wait_min   — tmin + queue_now × tpercar (minutes)
snapshot.tmin       — minimum crossing time (minutes)
snapshot.tpercar    — added time per vehicle (minutes)
snapshot.updated_at — when the queue data was recorded
snapshot.age_min    — minutes since last update
snapshot.source     — data source identifier

The data array (historical entries) is unchanged — this is a purely additive addition. Clients that do not read snapshot are unaffected.

Query all checkpoints on a given border + vehicle type in a single call instead of making one request per PPID.

GET /api/v1/data/border/{origin}/{destination}/{crossing_type}

• Supports a single destination country, a comma-separated list, or all to expand to every monitored neighbour at once.
• Results sorted by queue_now ascending (shortest queue first).
• Fully localized: add ?lang=uk (or any of our 22 supported languages) to get checkpoint names in that language.

Discover checkpoint PPID values by name without browsing the full directory.

GET /api/v1/data/search?name=Krakovets,Shehyni&lang=en

• Accepts a single name or comma-separated list (up to 20).
• Searches across all 24 translation languages — pass a name in Ukrainian, Polish, German or any supported language and it will match.
• Returns all PPIDs at that location grouped by vehicle type (car / bus / pedestrian / truck).

The alternatives product now accepts ?lang= in all 22 supported languages (was only 12).

New crossing_type parameter lets you override the vehicle type filter — e.g. pass crossing_type=4 to get car alternatives even when querying from a bus PPID.

The crossing_type_label field in checkpoints, border, and search responses is now translated to the requested language in all 22 supported languages. Country name fields (origin_name, destination_name) follow the same locale.

The Nakordoni Developer API portal is live at /en/developers. Sign up for a free Explorer key (200 requests/day) to access border queue data, forecasts, fuel prices, driver POIs and more.

Products available at launch: checkpoints, queue, stats, day-stats, forecast, alternatives, update_info, fuel, pois, truck_bans, trading_sundays, bus_carriers, road_conditions, assistant.