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 Alerts API

Create and manage threshold-based weather alerts that evaluate Tomorrow.io data layers against custom rules for linked locations and deliver notifications via webhook, email, and the Tomorrow.io app.

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

This API exposes 1 JSON Schema definition.

Tagged areas include Weather, Alerts, Webhook, and Notification. The published artifact set on APIs.io includes an API reference, an OpenAPI specification, and 1 JSON Schema.

This API exposes 10 operations across 7 paths, and defines 2 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.

10 operations 7 paths 2 schemas 1 DELETE3 GET5 POST1 PUT

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 Alerts 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 10

Across 7 paths, the API surfaces 10 operations — 1 DELETE, 3 GET, 5 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Alerts 10

Manage weather alerts and their location bindings.

GET
/alerts
List Alerts
listAlerts 1 param → 200
POST
/alerts
Create an Alert
createAlert 1 param body → 201
GET
/alerts/{alertId}
Retrieve an Alert
getAlert 2 params → 200
PUT
/alerts/{alertId}
Update an Alert
updateAlert 2 params body → 200
DELETE
/alerts/{alertId}
Delete an Alert
deleteAlert 2 params → 204
GET
/alerts/{alertId}/locations
List Alert Locations
listAlertLocations 2 params → 200
POST
/alerts/{alertId}/locations/link
Link Locations To Alert
linkAlertLocations 2 params body → 200
POST
/alerts/{alertId}/locations/unlink
Unlink Locations From Alert
unlinkAlertLocations 2 params body → 200
POST
/alerts/{alertId}/activate
Activate an Alert
activateAlert 2 params → 200
POST
/alerts/{alertId}/deactivate
Deactivate an Alert
deactivateAlert 2 params → 200

Schemas 2

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

AlertList
object
1 property
Alert
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Tomorrow.io publishes across the network.

Tomorrow.io Historical Weather API
Tomorrow.io Events API
Tomorrow.io Weather on Routes API
Tomorrow.io Locations 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 Alerts 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.