Approved road condition reports near borders and on major corridors: potholes, roadworks, closures, ice, hazards — combining driver reports with automatic accelerometer detections from our navigation app.
all (default) | user (our own driver reports only) | external (road-authority and provider feeds only)
limit
Max results (default 100, cap 500)
offset
Pagination offset (optional)
include_expired
1 = also return conditions whose expiry has passed (optional)
lang
Language for condition_type_name / severity_name labels — all 24 site languages (default uk)
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.conditions[].condition_type
What it is (roadworks, closure, accident, weather…), with condition_type_name in the requested language.
data.conditions[].severity
How bad it is, with severity_name.
data.conditions[].description
Free-text detail as published, with road_name and direction.
data.conditions[].latitude
Where it is, with longitude and country_code.
data.conditions[].corridor_ppid
The border crossing whose approach corridor this sits on, when it is on one.
data.conditions[].estimated_duration
How long it is expected to last, with expires_at and created_at.
data.conditions[].source
Upstream that reported it, with external_id — stable across refreshes, use it to deduplicate.
data.total
Matches for the query, with limit and offset for paging.
What's different in this version:
id is now a string carrying its real upstream identity (e.g. "gddkia_B29BE…", "tt_6a83…", "user_335") instead of v1's int, and condition_type keeps the raw upstream value instead of being folded into the v1 enum. The response adds the completeness trio returned / total_available / truncated, plus scope (radius | corridor_ppid | corridor_country). New in v2: ?air_alerts=1 attaches a coarse air-raid advisory (region codes only) for the same scope — the full picture lives in the separate "air-alerts" product. v1 keeps its exact shape — external rows there get a stable negative int id and carry their real id in the additive `external_id` key.
Live road conditions on the approaches to a border crossing: accidents, roadworks, closures, congestion, weather hazards, potholes and ice. Merges our own driver reports with the incident feeds we run the navigator on — national road authorities (GDDKiA, autobahn.de, ÖAMTC, Zjazdnost, Digitraffic, CCISS, DGT) plus TomTom, HERE and crowd reports — deduplicated across sources, each row carrying the `source` it came from. Without coordinates the answer is scoped to the BORDER CORRIDORS rather than a whole country: the last 50 km of the main road from each capital to the crossing, on both sides of the border. Pass ?ppid= for one crossing, or lat/lng+radius for a plain radius search anywhere.
ISO-2 country code (optional). Returns that country's side of the border corridors — not a country-wide dump
ppid
Checkpoint ID, e.g. id_13 (optional). Scopes the answer to that crossing's corridor: the last 50 km of the main road to it on BOTH sides of the border
condition_type
accident|roadwork|closure|congestion|weather|hazard|pothole|speed_bump|object|stopped|ice|other (optional). v2 returns the raw upstream value, so a feed reporting police or event is not folded into `other`
severity
low|moderate|major|critical (optional)
lat
Latitude (optional) — with lng, switches to a plain radius search
lng
Longitude (optional)
radius
Radius km (default 50). Applies ONLY with lat+lng; on the corridor path the road itself is the filter, not a circle
sources
all (default) | user (our own driver reports only) | external (road-authority and provider feeds only)
air_alerts
1 = add an `air_alerts` advisory block for the same scope: whether any region is under an air-raid alert, as ISO 3166-2 region codes, with as_of / lag_min (default 0). Deliberately coarse — no distances, no proximity bands, no tracked objects. For those, call the separate Air Alert Proximity API (product "air-alerts", /api/v2/data/air-alerts?ppid=id_94&radius_km=100), which is built around the safety constraints they need. Ukraine only; a request scoped to another country gets applicable:false rather than an empty list
limit
Max results (default 100, cap 500)
offset
Pagination offset (optional)
include_expired
1 = also return conditions whose expiry has passed (optional)
lang
Language for condition_type_name / severity_name labels — all 24 site languages (default uk)
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.conditions[].condition_type
What it is (roadworks, closure, accident, weather…), with condition_type_name in the requested language.
data.conditions[].severity
How bad it is, with severity_name.
data.conditions[].description
Free-text detail as published, with road_name and direction.
data.conditions[].latitude
Where it is, with longitude and country_code.
data.conditions[].corridor_ppid
The border crossing whose approach corridor this sits on, when it is on one.
data.conditions[].estimated_duration
How long it is expected to last, with expires_at and created_at.
data.conditions[].source
Upstream that reported it, with external_id — stable across refreshes, use it to deduplicate.
data.total
Matches for the query, with limit and offset for paging.
