Discover/meteo API
live

meteo APImeteo.pl

Access ICM UW weather forecasts via API. Get hourly temperature, wind, pressure, and precipitation from UM and GFS models for any location.

This API takes change requests — .
Endpoint health
verified 1d ago
get_available_forecasts
get_forecast
search_location
3/3 passing latest checkself-healing
Endpoints
3
Updated
1d ago

What is the meteo API?

The meteo.pl API provides 3 endpoints to access detailed numerical weather forecasts from Poland's Interdisciplinary Centre for Mathematical and Computational Modelling (ICM UW). The get_forecast endpoint returns hourly time-series data covering temperature, sea-level pressure, wind, precipitation, and cloud parameters for any coordinates, driven by the UM (4 km resolution, Central Europe) and GFS (global) forecast models.

This call costs1 credit / call— charged only on success
Try it
City name or location query (e.g. 'Warsaw', 'Krakow').
api.parse.bot/scraper/42cc9553-a71b-4a4e-820c-56bbd6760c9d/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/42cc9553-a71b-4a4e-820c-56bbd6760c9d/search_location?query=Warsaw' \
  -H 'X-API-Key: $PARSE_API_KEY'
All endpoints · 3 totalmissing one? ·

Search for a location by name to get coordinates, display name, and address details. Returns up to 5 matching results from the geocoding service. Each result includes latitude, longitude, display_name, address components, and OpenStreetMap metadata. Use to resolve a city name into coordinates for get_forecast.

Input
ParamTypeDescription
queryrequiredstringCity name or location query (e.g. 'Warsaw', 'Krakow').
Response
{
  "type": "object",
  "fields": {
    "results": "array of location objects with lat, lon, display_name, address, and OpenStreetMap metadata"
  },
  "sample": {
    "data": {
      "results": [
        {
          "lat": "52.2319581",
          "lon": "21.0067249",
          "type": "city",
          "class": "place",
          "osm_id": 336075,
          "address": {
            "city": "Warszawa",
            "state": "mazowieckie",
            "country": "Polska",
            "country_code": "pl"
          },
          "licence": "Data OpenStreetMap contributors, ODbL 1.0.",
          "osm_type": "relation",
          "place_id": 767705185,
          "importance": 0,
          "display_name": "Warszawa, mazowieckie, Polska"
        }
      ]
    },
    "status": "success"
  }
}

About the meteo API

Location Search and Geocoding

Before fetching a forecast, use search_location with a query parameter (city name or address string) to resolve a place to coordinates. The endpoint returns up to 5 candidate results, each containing lat, lon, display_name, and a structured address object with OpenStreetMap metadata. Pass the resolved lat and lon directly to get_forecast, or supply a location string and let the API geocode it internally.

Forecast Models and Run Timestamps

get_available_forecasts returns the timestamps of available model runs as Unix epoch integers, grouped by model key: gfs (global), um4_60 (UM 4 km, 60-hour horizon for Central Europe), and um4_120 (UM 4 km, 120-hour horizon). Use these timestamps to pass a specific date parameter to get_forecast, or omit date to default to the latest available run. The model choice affects both spatial resolution and forecast horizon.

Hourly Forecast Data

get_forecast accepts lat/lon or a location name, an optional model string (um4_60, um4_120, or gfs), and an optional Unix date for the desired model run. The response contains a forecast array of hourly entries keyed by date_time, with meteorological fields including airtmp_point (air temperature), slpres_point (sea-level pressure), wind10_sd_true_prev_poi (10 m wind), and precipitation and cloud coverage fields. The location object in the response confirms the resolved lat, lon, and display_name. The metadata object records the model name, run_timestamp, and forecast_start.

Coverage Notes

The UM model covers Central Europe at 4 km resolution with either a 60-hour or 120-hour lookahead depending on the selected variant. The GFS model covers global coordinates but at coarser resolution. Both models are produced by ICM UW at the University of Warsaw and are updated on a regular run schedule reflected in the timestamps returned by get_available_forecasts.

Reliability & maintenanceVerified

The meteo API is a managed, monitored endpoint for meteo.pl — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when meteo.pl 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 meteo.pl 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.

Last verified
1d ago
Latest check
3/3 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Display hourly temperature and wind forecasts for Polish cities in a travel or event planning app using get_forecast with UM 4 km resolution.
  • Monitor sea-level pressure trends at specific coordinates for agricultural scheduling by parsing the slpres_point field in the forecast time series.
  • Build a Central European weather dashboard that surfaces the latest available UM and GFS run times via get_available_forecasts.
  • Geocode user-entered city names to coordinates with search_location before feeding them into downstream forecast requests.
  • Compare 60-hour and 120-hour UM model outputs for the same location by calling get_forecast twice with different model values.
  • Trigger weather-based logistics alerts when precipitation fields in the hourly forecast exceed operational thresholds.
  • Archive historical model run data by recording the run_timestamp and full forecast arrays from successive get_forecast calls.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 req/min

Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does meteo.pl provide an official developer API?+
ICM UW does not publish a documented public REST API for external developers. The meteo.pl website is intended as a consumer forecast service for end users, not a programmatic data feed.
What meteorological fields does `get_forecast` actually return?+
Each hourly entry in the forecast array includes date_time, air temperature (airtmp_point), sea-level pressure (slpres_point), 10 m wind speed and direction (wind10_sd_true_prev_poi), and precipitation and cloud coverage parameters. The metadata object records which model was used, its run_timestamp, and the forecast_start time.
Does the UM model cover locations outside Central Europe?+
The um4_60 and um4_120 models are limited to Central Europe. For locations outside that region, the gfs model covers global coordinates at coarser resolution. If you request a UM forecast for a point outside its grid, the API auto-selects a model, or you can explicitly pass model: 'gfs'.
Can the API return ensemble forecasts or probabilistic data?+
Not currently. The API returns deterministic hourly forecast values from the UM and GFS models; ensemble spread or probability-of-precipitation percentiles are not part of the current response schema. You can fork the API on Parse and revise it to add ensemble fields if ICM UW exposes that data.
Are historical observed weather conditions available through this API?+
Not currently. The three endpoints cover location search, model run timestamps, and forward-looking forecast data only — observed station measurements or reanalysis records are not exposed. You can fork the API on Parse and revise it to add a historical observations endpoint if you need that data.
Page content last updated . Spec covers 3 endpoints from meteo.pl.
Related APIs in WeatherSee all →
weatherforecast.com API
Get detailed 12-day weather forecasts for any location worldwide, with temperature, wind, rain, humidity, and UV index data updated three times daily. Search locations and retrieve comprehensive weather information suitable for travel planning, research, and general forecasting needs.
metoffice.gov.uk API
Access detailed UK weather forecasts, real-time lightning tracking, and weather warnings from the Met Office. Search locations to retrieve hourly, daily, regional, and long-range predictions, and monitor storm activity with spot forecasts across any geographic area.
openweathermap.org API
Search for cities and retrieve live weather conditions and forecasts (current, minutely precipitation, hourly and daily) by coordinates or by city name.
weatherunderground.com API
Get real-time weather data and 10-day forecasts for any location, with access to current conditions like temperature, humidity, and wind speed. Search for locations and receive detailed weather narratives to plan your day or week ahead.
bom.gov.au API
Get accurate weather forecasts for Australian cities with temperature, precipitation, UV index, and conditions from the Bureau of Meteorology. Search for any location and retrieve multi-day forecasts to plan your activities with confidence.
accuweather.com API
Get real-time weather conditions, multi-day forecasts, and health alerts for any location worldwide. Search cities and access detailed data including allergen information and air quality to plan your activities with confidence.
smhi.se API
Get accurate weather forecasts, current conditions, and severe weather warnings for any location across Sweden. Search for specific Swedish locations to retrieve detailed meteorological analysis and real-time weather data.
weatherspark.com API
Get historical weather data, current METAR reports, and monthly climate summaries for any location by searching WeatherSpark's comprehensive weather database. Access detailed weather insights including temperature trends, precipitation patterns, and atmospheric conditions to power weather-dependent applications and analysis.