WeatherForecast APIweatherforecast.com ↗
Access 12-day weather forecasts from weatherforecast.com via 2 endpoints. Get temperature, wind, rain, humidity, and UV index for any location worldwide.
What is the WeatherForecast API?
The WeatherForecast.com API provides 12-day weather forecasts for locations worldwide through 2 endpoints: search_location to resolve a city or country name to a canonical slug, and get_forecast to retrieve structured forecast data covering up to 36 periods per location (3 per day: AM, PM, Night). Each period includes temperature, wind, rain, humidity, UV index, and feels-like values.
curl -X GET 'https://api.parse.bot/scraper/e084886e-f8e2-4450-9a25-3440ef2da151/search_location?query=London' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace weatherforecast-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.global_weather_forecast_api import WeatherForecast, Location, Forecast, ForecastPeriod
client = WeatherForecast()
# Search for a location
location = client.locations.search(query="Tokyo")
print(location.slug, location.url)
# Get the forecast for that location
forecast = location.forecast()
print(forecast.location, forecast.forecast_url)
print(forecast.details.elevation, forecast.details.coordinates)
# Iterate over forecast periods
for period in forecast.forecasts:
print(period.day, period.time, period.summary, period.temp_high, period.rain_mm)
Search for a location by name using the autocomplete service and return its canonical slug and forecast URL. The slug identifies the location for get_forecast. Returns the first matching result from the autocomplete index; partial names and common city names resolve to the most prominent match.
| 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/London/forecasts/latest",
"slug": "London",
"query": "London"
},
"status": "success"
}
}About the WeatherForecast API
Endpoints
The API exposes two endpoints. search_location accepts a query string — a city name, country, or partial name — and returns the canonical slug and forecast url for the best-matching location. This slug is the required input for get_forecast. Slugs follow patterns like London, Tokyo-1, or New-York-1, reflecting the site's internal location index.
Forecast Data
get_forecast accepts a slug and returns a forecasts array covering 12 days at 3 time periods per day (AM, PM, Night). Each period object carries day, time, summary, temp_high, temp_low, feels_like, wind, rain_mm, humidity_pct, and uv_index. The response also includes a details object with text, elevation, population, and coordinates for the location, plus a location string and a forecast_url.
Coverage and Freshness
The data covers locations globally. Resolution depends on how well the source index matches the supplied query — common city names typically resolve immediately, while ambiguous names (e.g., "Springfield") return the most prominent match. The search_location endpoint processes partial names, so you can supply incomplete strings and still get a usable slug.
Data Shape Notes
Temperature values are provided per period as both temp_high and temp_low, alongside feels_like. Wind is a single field per period; the API does not split wind speed and direction into separate fields in the current response shape. The freeze_level field is included in the forecast period objects where applicable.
The WeatherForecast API is a managed, monitored endpoint for weatherforecast.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when weatherforecast.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official weatherforecast.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Display a 12-day trip forecast broken into AM/PM/Night periods for a travel itinerary app
- Monitor daily UV index and humidity across multiple cities for health or agriculture dashboards
- Collect rain_mm forecasts for outdoor event scheduling or logistics planning
- Batch-resolve city slugs via search_location and store forecast data for offline analysis
- Track feels_like temperatures alongside wind data to calculate apparent weather conditions
- Generate location-specific weather summaries using the details object's elevation and coordinates
| 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 | 100 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.