For developers
API docs
DailyMeteo exposes two read endpoints over the same data and the same query parameters — they differ only in how the response comes back. Pick pq for a normal request/response call, or graph when you want the values as they arrive instead of waiting for the whole payload.
01 · Endpoints
pq vs. graph
GET/meteo/v2/pq/
Point query
Buffered — the response is a single JSON array returned once the whole query has been resolved. Simplest to use for one location, one day, or a short range.
GET/meteo/v2/graph/
Streaming
Same query, same data — but the body streams back incrementally as it's produced, so long ranges start returning data immediately instead of one slow round trip.
Both live under https://api.dailymeteo.com and need an api_key — see the API key docs if you don't have one yet.
02 · Parameters
Shared query parameters
These apply to both endpoints identically.
| Param | Meaning |
|---|---|
var | Variable to query — e.g. tmin, tmax, tmean, prcp. |
agg_level | agg for observed data, ltm for long-term (climate normal) averages. |
time_scale | Granularity of the returned values — day, mon, or ann. |
lat / lon | Location as decimal degrees. |
api_key | Your API key. |
time | One or more comma-separated dates — returns one value per date. Format depends on time_scale: YYYY-MM-DD for day, YYYY-MM for mon, YYYY for ann. |
from / to | A date range — returns one value per step in range. Same time_scale-dependent format as time above. Use instead of time, not alongside it. |
03 · Point query
GET/meteo/v2/pq/
Returns the whole result set as one JSON array of { timestamp, value } objects, in chronological order.
https://api.dailymeteo.com/meteo/v2/pq/?var=tmin&agg_level=agg&time_scale=day&lat=44.8153318&lon=20.4456588&api_key=YOUR_API_KEY&from=2020-12-22&to=2020-12-25Response
[
{ "timestamp": "2020-12-22", "value": -2.1 },
{ "timestamp": "2020-12-23", "value": -0.8 },
{ "timestamp": "2020-12-24", "value": 1.4 },
{ "timestamp": "2020-12-25", "value": 3.0 }
]04 · Streaming
GET/meteo/v2/graph/
Same request shape as pq, but the response is sent as it's produced rather than assembled up front — worth reaching for once a range spans enough points that buffering the whole thing would be slow.
https://api.dailymeteo.com/meteo/v2/graph/?var=tmin&agg_level=agg&time_scale=day&lat=44.8153318&lon=20.4456588&api_key=YOUR_API_KEY&from=1961-01-01&to=2020-12-31The wire format depends on time_scale:
time_scale=dayNot JSON — a stream of
timestamp,valuepairs separated by;, so you can parse and plot each record as it arrives instead of waiting for a closing bracket.2020-12-22,-2.1;2020-12-23,-0.8;2020-12-24,1.4;2020-12-25,3.0;...time_scale=mon/annA single JSON array, same shape as
pq's response — just sent over a chunked transfer so a client can start reading objects out of it before the array closes.