The APIs¶
One subpackage per Open-Meteo service, each with a page of its own.
Every subpackage follows the same shape: a client preset to the
service’s base URL, one operation class per endpoint (GetV1Forecast,
SearchLocations, …), enums for the enumerable request parameters,
and dataclass models for the responses. Import everything from the
subpackage root — e.g. from action0.open_meteo.marine import MarineClient.
Subpackage |
Client |
Default base URL |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Common to all weather services: coordinates are strings (the APIs
accept comma-separated multi-location requests), the response blocks
are parallel lists with *_units companions, unrequested blocks come
back None, and timezone="auto" resolves the local time zone.
Commercial subscriptions pass apikey= on the operations and the
customer--prefixed host as the client’s base_url.