v4
latestOpenAPI 3.1.0Proprietary2026-08-034715226.2 KBQuery truck restrictions along a corridor
Returns all truck-related restrictions within a buffer around the straight-line path between two points. Uses PostGIS spatial intersection (ST_Buffer + ST_Intersects).
Searches across feature types: bridge_clearances, bridges, weight_restrictions, truck_restrictions, truck_routes, freight_corridors, truck_parking.
Results are ordered by distance from the corridor centerline. Each feature includes _distance_km in its properties.
Only restrictions in force now are returned: a feature whose active window has ended, or has not begun, is excluded. Seasonal limits (spring load restrictions) carry their window on start_time/end_time and are otherwise live year-round.
This endpoint does not filter by vehicle dimensions. height and weight are rejected with a 400 rather than accepted, because upstream feeds publish no normalized clearance or weight for roughly 97% of the structures along a corridor. Filtering on what little is normalized would drop everything we cannot judge, and a short list reads as "this route is clear" — the one wrong answer that matters.
This endpoint gives you the inventory along the corridor; deciding what conflicts with a specific vehicle is yours to do, or use POST /routing/route, which follows a real route and emits a warning per restriction it can actually evaluate against the truck profile.
Requires Pro+ plan with truck data access.
Query parameters
Origin latitude
Origin longitude
Destination latitude
Destination longitude
Buffer distance around corridor in km (default 5, max 50)
Filter by jurisdiction code (e.g., WA, NY, ON)
Maximum results (default 500, max 2000)
Response
Corridor restrictions with metadata