weatherforecast.com APIweatherforecast.com ↗
Get worldwide 12-day weather forecasts from WeatherForecast.com. Three periods per day with temperature, wind, rain, humidity, and UV index data.
curl -X GET 'https://api.parse.bot/scraper/e084886e-f8e2-4450-9a25-3440ef2da151/search_location?query=Tokyo' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for a location by name using the autocomplete service and return its canonical slug and forecast URL. The slug can be passed to get_forecast to retrieve the full weather data.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | City or country name to search for (e.g. 'London', 'Tokyo', 'Springfield'). |
{
"type": "object",
"fields": {
"url": "string - full URL to the location's forecast page",
"slug": "string - canonical location slug for use with get_forecast",
"query": "string - the original search query"
},
"sample": {
"data": {
"url": "https://www.weather-forecast.com/locations/Tokyo-1/forecasts/latest",
"slug": "Tokyo-1",
"query": "Tokyo"
},
"status": "success"
}
}About the weatherforecast.com API
The WeatherForecast.com API exposes 2 endpoints covering worldwide location search and 12-day weather forecasts, returning up to 36 forecast periods per location. The get_forecast endpoint delivers temperature highs and lows, feels-like temperature, wind speed, rainfall in millimeters, humidity percentage, UV index, and freeze level data across three daily periods (AM, PM, Night). Location slugs are resolved via the search_location endpoint before fetching forecast data.
Endpoints
The API consists of two endpoints. search_location accepts a query string (city or country name) and returns a canonical slug, the original query, and a full forecast page url. This slug is the required input to get_forecast — slugs follow patterns like London, Tokyo-1, or New-York-1 and are not always predictable from the city name alone, so resolving them through search_location first is the correct workflow.
Forecast Data Shape
get_forecast accepts a slug and returns a details object containing the location's text description, elevation, population, and coordinates. The forecasts array contains one object per forecast period, each tagged with day, time (AM / PM / Night), and a summary label. Numerical fields per period include temp_high, temp_low, feels_like, wind, rain_mm, humidity_pct, uv_index, and freeze level data. The forecast covers 12 days, yielding up to 36 period objects per response.
Coverage and Freshness
Forecasts are worldwide in scope. The details object supplements weather data with geographic context — elevation and population figures are included alongside latitude/longitude coordinates, which makes the response useful for applications that need to cross-reference location metadata alongside forecast conditions. The forecast_url field in the response points back to the source page for the queried location.
- Travel itinerary tools that surface rain probability and UV index for trip dates using
get_forecast - Agricultural planning dashboards that monitor
rain_mmandhumidity_pctover a 12-day window - Outdoor event scheduling systems that check AM/PM/Night temperature and wind forecasts for a venue location
- Elevation-aware hiking or mountaineering apps that use the freeze level and elevation fields from
details - Research pipelines that batch
search_locationqueries to resolve canonical slugs for a list of cities before pulling forecast data - UV exposure monitoring tools for health or dermatology applications using the
uv_indexfield - Logistics or shipping dashboards that surface feels-like temperature and wind data for driver or route planning
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does WeatherForecast.com have an official developer API?+
What does the `search_location` endpoint return, and why is it needed before calling `get_forecast`?+
search_location returns a slug, the original query, and a forecast page url for the matched location. The slug is the required input to get_forecast, and slugs are not always a simple city name — Tokyo resolves to Tokyo-1 and New York to New-York-1, for example — so using search_location first is the reliable way to obtain a valid slug before fetching forecast data.Are hourly forecasts available, or only the three daily periods?+
Does `get_forecast` include historical weather data?+
What geographic metadata does the API include alongside forecast data?+
details object in the get_forecast response includes the location's elevation, population, coordinates (latitude/longitude), and a text description. These fields are returned alongside the forecast array, so you can use elevation or coordinates for downstream calculations without a separate geocoding call.