wetter APIwetter.com ↗
Get 16-day daily weather forecasts from wetter.com. Returns high and low temperatures in Celsius for any city or region via a single endpoint.
What is the wetter API?
The wetter.com API provides a 16-day weather forecast for any searchable location through a single get_forecast endpoint. Each response includes a full location string with postal code and country, plus an array of daily forecast objects covering date, high temperature, and low temperature in Celsius. It supports German, European, and international city lookups by name.
curl -X GET 'https://api.parse.bot/scraper/36ab87de-9230-4efe-a3fe-16c63009e6fb/get_forecast?days=16&location=Berlin' \ -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 wetter-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.wetter_com_forecast_api import Wetter, Forecast, DailyForecast
client = Wetter()
forecast = client.forecasts.get(location="Berlin")
print(forecast.location)
for day in forecast.forecast:
print(day.date, day.temp_high, day.temp_low)
Get 16-day weather forecast for a given location. Searches wetter.com for the location and returns daily high and low temperatures in Celsius for each forecast day. Returns up to 16 days of forecast data starting from today. The location search supports German and international city names.
| Param | Type | Description |
|---|---|---|
| locationrequired | string | City name or location identifier (e.g. "Berlin", "München", "London"). |
{
"type": "object",
"fields": {
"forecast": "array of daily forecast objects, each containing date (YYYY-MM-DD), temp_high (integer Celsius), and temp_low (integer Celsius)",
"location": "string, full location name with postal code and country"
},
"sample": {
"data": {
"forecast": [
{
"date": "2026-06-10",
"temp_low": 10,
"temp_high": 19
},
{
"date": "2026-06-11",
"temp_low": 11,
"temp_high": 18
}
],
"location": "Berlin - 10178 - Hauptstadt Deutschland"
},
"status": "success"
}
}About the wetter API
What the API Returns
The get_forecast endpoint accepts a location string — a city name or identifier such as "Berlin", "München", or "London" — and returns a structured forecast object. The top-level location field gives the resolved full location name including postal code and country, which is useful for confirming the lookup matched the intended place. The forecast array contains one object per day, each with date, temp_high (daily maximum in °C), and temp_low (daily minimum in °C), spanning up to 16 days from the request date.
Data Coverage
The forecast range covers 16 days, making it suitable for medium-range planning. Temperature values are always in Celsius. Location matching follows wetter.com's own search, which has strong coverage of German-speaking regions and broad coverage of European and major international cities. If a location string matches multiple places, the API returns the top-matched result.
Inputs and Behavior
The only required parameter is location. Passing a well-known city name is sufficient for most lookups. More specific inputs — such as including a country name or district — can help disambiguate results where multiple cities share a name. There are no optional filter parameters; the endpoint always returns the full 16-day window.
The wetter API is a managed, monitored endpoint for wetter.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when wetter.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 wetter.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 two-week temperature outlook widget for a given city in a travel planning app
- Alert users when forecasted high temperatures exceed a threshold for outdoor event scheduling
- Compare daily highs and lows across multiple European cities for agricultural or logistics planning
- Build a historical-style temperature trend chart by polling the API daily and storing
temp_highandtemp_lowvalues - Populate destination weather summaries in a hotel or vacation rental booking flow using the resolved
locationfield - Notify field service teams of low-temperature forecasts that could affect equipment or scheduling
| 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.
Does wetter.com offer an official developer API?+
What exactly does get_forecast return for each day?+
forecast array contains three fields: date (the calendar date for that forecast day), temp_high (the expected daily maximum in Celsius), and temp_low (the expected daily minimum in Celsius). The root-level location field provides the resolved full location name with postal code and country.Does the API return hourly forecasts or precipitation data?+
How precise is the location matching?+
location field shows the full resolved name including postal code and country, so you can verify which place was matched. For ambiguous city names, passing a more specific string (e.g. including a country or region) improves match accuracy.Can I retrieve forecasts for multiple locations in a single request?+
get_forecast endpoint accepts one location per call. Fetching forecasts for multiple cities requires one request per location. You can fork this API on Parse and revise it to batch multiple location lookups into a single response if your use case requires it.