route.json returns the forecast along a journey at the time the vehicle is expected at each point: give the route and the
departure time (and speed), and every sampled point gets the hourly forecast for its estimated arrival time, with a summary and plain
warnings (heavy rain, snow or ice, strong gusts, poor visibility, thunderstorms) for dispatchers, drivers and fleet apps.
Available on Pro+ plan and above. Keys on other plans receive error code 2009. Each sampled point counts as one API call (like bulk requests), up to 60 points a request.
Example requests
https://api.weatherapi.com/v1/route.json?key=<YOUR_API_KEY>&q=51.5074,-0.1278&points=52.4862,-1.8904;53.4808,-2.2426&depart=2026-11-05 07:30&speed_kph=80
https://api.weatherapi.com/v1/route.json?key=<YOUR_API_KEY>&q=Seattle&polyline=<encoded polyline from your routing service>&interval_km=25
Or POST JSON (with q as any point on the route) to give your own arrival times:
POST https://api.weatherapi.com/v1/route.json?key=<YOUR_API_KEY>&q=40.71,-74.01
{"points":[{"lat":40.71,"lon":-74.01,"eta":1793865600},{"lat":39.95,"lon":-75.17,"eta":1793871000},{"lat":38.90,"lon":-77.04,"eta":1793880000}]}
Request parameters
| Parameter | Required | Description |
|---|
| key | Yes | Your API key. |
| q | Yes | The start of the route (any location format). With polyline or a POST body the route comes from those, and q gives the location block. |
| points | One of these | The rest of the route after q: lat,lon;lat,lon;..., up to 2,000 points. |
| polyline | One of these | The whole route as an encoded polyline (Google format), as returned by most routing services. precision=6 for 6-digit polylines. |
| depart | No | Departure time: Unix time or yyyy-MM-dd HH:mm (UTC). Default now. The journey must end within 10 days. |
| speed_kph | No | Average speed used for arrival times, 5 to 300. Default 70. |
| interval_km | No | Distance between sampled points, 1 to 500. Default 20; long routes are sampled more sparsely to stay within 60 points. |
Response
route.distance_km, distance_miles, depart_epoch, arrive_epoch, duration_min and samples;
route.summary: min_temp_c, max_temp_c, max_wind_kph, max_gust_kph, max_precip_mm, min_vis_km and warnings (text, with where and when);
route.points: one entry per sample with km, lat, lon, eta_epoch, eta_utc, forecast_time_epoch, temp_c, temp_f, feelslike_c, condition (text, code), is_day, wind_kph, wind_degree, gust_kph, precip_mm, chance_of_rain, chance_of_snow, vis_km and humidity.
Distances are along the straight lines between your points, so give enough points (or a polyline) to follow the roads. Invalid parameters return HTTP 400 with error code 1015.