European truck driving restrictions for one or more countries, including seasonal and holiday bans. Each ban carries its restriction type (General / Local / Sunday / Holiday / Seasonal), the exact scope or roads affected and the minimum weight, and each country a live status computed in its own timezone (active_window / next_window), plus a covered_countries list. Scoped per country: country is required and accepts a comma-separated list of up to 10 codes. The response also reports returned, total_available and truncated, so a capped answer is never mistaken for a complete one.
ISO-2 country code, or a comma-separated list of up to 3, e.g. RO or DE,RO. More than 3 is refused. Optional in v1; required in v2.
lang
Language code for country names and summary (default en)
include_ua_heat
1 = also return Ukraine's computed summer heat ban (trucks >24 t banned 10:00-22:00 when forecast temp >+28 °C), per oblast. Included automatically when Ukraine is in scope (country=UA) — this flag only adds it to a request scoped to some other country
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.current_bans[]
Bans in force right now, same fields as upcoming_bans. is_ban_active is the quick boolean for 'may a truck drive at this moment'.
data.upcoming_bans[].date
Ban day, with time_from and time_until in local time.
data.upcoming_bans[].country_code
Country the ban applies in, with country_name.
data.upcoming_bans[].restriction_type
What kind of ban it is (weekend, holiday, heat…), with restriction_details in the requested language.
data.upcoming_bans[].min_weight_tons
Weight from which the ban bites — a lighter truck is unaffected.
data.upcoming_bans[].details_url
Official source page for that ban.
data.bans_by_country
The same bans grouped by ISO-2 country, for rendering per country.
data.window
The period covered: from, to, days and whether you requested it.
data.total_bans
Bans in the window, with returned, total_available and truncated — true means narrow the window or page.
data.covered_countries
Countries we track bans for; countries_not_covered names the ones you asked about that we do not.
data.summary
One-sentence plain-language summary, ready to show a driver. as_of is when it was assembled.
data.ua_heat_ban
Ukraine's computed heat ban (see include_ua_heat): per-oblast status plus forecast_horizon, the last date the underlying weather forecast reaches. Heat rows are never returned past that date, so compare it with data.window before reading an empty answer as 'no ban'.
What's different in this version:
country is now required. v2 is scoped per country and refuses an unscoped request with 400 scope_required; it accepts a comma-separated list of up to 3 codes, so one request still covers the countries on a route. v2 also honours a DATE WINDOW — ?date= for one day, or ?date_from=/?date_to= for a range of up to 92 days, starting at most 7 days in the past and running forward to 2028-12-31 — where v1 always answers a fixed 7-day window and ignores any date sent to it. Every response now echoes `window` {from,to,days,requested} so the served range is never in doubt. v1 continues to accept an unscoped call, which returns a capped slice — check truncated and total_available in the response.
European truck driving restrictions for one or more countries, including seasonal and holiday bans. Each ban carries its restriction type (General / Local / Sunday / Holiday / Seasonal), the exact scope or roads affected and the minimum weight, and each country a live status computed in its own timezone (active_window / next_window), plus a covered_countries list. ?country= accepts a comma-separated list of up to 3 codes; it is optional in v1 and required in v2. The response also reports `returned`, `total_available` and `truncated` so a capped answer is never mistaken for a complete one, plus `window` {from,to,days} naming the exact date range it covers. v1 always covers the next 7 days; v2 additionally accepts ?date= / ?date_from= + ?date_to= for any window up to 92 days, beginning at most 7 days in the past (this is a forward-looking calendar — older history is refused with 400 date_too_old) and running forward to 2028-12-31.
ISO-2 country code, or a comma-separated list of up to 3, e.g. RO or DE,RO. Required in v2; more than 3 is refused with 400 too_many_countries — split the request.
date
Single day as YYYY-MM-DD. Cannot be combined with date_from/date_to.
date_from
Start of the window (YYYY-MM-DD, inclusive). Defaults to today when only date_to is given.
date_to
End of the window (YYYY-MM-DD, inclusive). Defaults to date_from + 7 days. The window may span at most 92 days — a longer range is refused with 400 date_range_too_long rather than silently cut. This is a forward-looking calendar: a window may start at most 7 days in the past (400 date_too_old beyond that, naming the earliest date you may ask for), and runs forward to 2028-12-31. History is not served — the product tells you what applies from now on, not what applied last spring.
lang
Language code for country names and summary (default en)
include_ua_heat
1 = also return Ukraine's computed summer heat ban (trucks >24 t banned 10:00-22:00 when forecast temp >+28 °C), per oblast. Included automatically when Ukraine is in scope (country=UA) — this flag only adds it to a request scoped to some other country. It is computed from a weather forecast, not read from the ban calendar, so it answers only for the part of your date window the forecast reaches: never the past, and never beyond ua_heat_ban.forecast_horizon (about a week out). A window entirely beyond that horizon returns no heat rows and says so in summary — it does not mean there will be no ban
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.current_bans[]
Bans in force right now, same fields as upcoming_bans. is_ban_active is the quick boolean for 'may a truck drive at this moment'.
data.upcoming_bans[].date
Ban day, with time_from and time_until in local time.
data.upcoming_bans[].country_code
Country the ban applies in, with country_name.
data.upcoming_bans[].restriction_type
What kind of ban it is (weekend, holiday, heat…), with restriction_details in the requested language.
data.upcoming_bans[].min_weight_tons
Weight from which the ban bites — a lighter truck is unaffected.
data.upcoming_bans[].details_url
Official source page for that ban.
data.bans_by_country
The same bans grouped by ISO-2 country, for rendering per country.
data.window
The period covered: from, to, days and whether you requested it.
data.total_bans
Bans in the window, with returned, total_available and truncated — true means narrow the window or page.
data.covered_countries
Countries we track bans for; countries_not_covered names the ones you asked about that we do not.
data.summary
One-sentence plain-language summary, ready to show a driver. as_of is when it was assembled.
data.ua_heat_ban
Ukraine's computed heat ban (see include_ua_heat): per-oblast status plus forecast_horizon, the last date the underlying weather forecast reaches. Heat rows are never returned past that date, so compare it with data.window before reading an empty answer as 'no ban'.
