How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Tomorrow.io Historical Weather API

Retrieve historical weather observations and monthly climate normals for any point or polygon on Earth using the same field catalog as the realtime and forecast APIs.

Tomorrow.io Historical Weather API is one of 10 APIs that Tomorrow.io publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Weather, Historical, Climate, and Climate Normals. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 2 operations across 2 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 4.0.

Requests are made against a single base URL, https://api.tomorrow.io/v4.

2 operations 2 paths 4 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
4.0
Base URL
https://api.tomorrow.io/v4
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Tomorrow.io Historical Weather API declares 1 security scheme for authenticating requests. An API key is passed in the query as apikey (apikeyAuth). By default, every request must be authenticated.

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Historical 2

Retrieve historical weather data and climate normals.

POST
/historical
Retrieve Historical Timeline
postHistorical 1 param body → 200401429
GET
/historical/climate/normals
Get Climate Normals
getClimateNormals 3 params → 200401429

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are HistoricalRequest (7 properties), ErrorResponse (3 properties), ClimateNormalsResponse (2 properties), HistoricalResponse (1 property). Each schema is shown below with its type and property counts.

ErrorResponse
object
3 properties
HistoricalRequest
object
7 properties 5 required
ClimateNormalsResponse
object
2 properties
HistoricalResponse
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tomorrow-io-historical-api-openapi.yml Raw ↑

Other APIs Tomorrow.io publishes across the network.

Tomorrow.io Events API
Tomorrow.io Weather on Routes API
Tomorrow.io Locations API
Tomorrow.io Alerts API
Tomorrow.io Insights API
Tomorrow.io Forecast API
Tomorrow.io Maps API
Tomorrow.io Realtime API
Tomorrow.io Timelines API
Where this information came from

This is an independent, third-party profile of Tomorrow.io Historical Weather API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.