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

Persistent alerts linked to one or more locations with webhook delivery.

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

Tagged areas include Alerts. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and code examples.

This API exposes 10 operations across 7 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 4.0.1.

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

10 operations 7 paths 7 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.1
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 (apiKeyQuery). By default, every request must be authenticated.

  • apiKeyQuery — Tomorrow.io API key passed as apikey query parameter. Obtain at https://app.tomorrow.io/development/keys.

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

Persistent alerts linked to one or more locations with webhook delivery.

GET
/alerts
Tomorrow.io List Alerts
listAlerts → 200401
POST
/alerts
Tomorrow.io Create Alert
createAlert body → 201400
GET
/alerts/{alertId}
Tomorrow.io Get Alert
getAlert 1 param → 200404
PUT
/alerts/{alertId}
Tomorrow.io Update Alert
updateAlert 1 param body → 200404
DELETE
/alerts/{alertId}
Tomorrow.io Delete Alert
deleteAlert 1 param → 204404
GET
/alerts/{alertId}/locations
Tomorrow.io List Alert Locations
listAlertLocations 1 param → 200
POST
/alerts/{alertId}/locations/link
Tomorrow.io Link Alert Locations
linkAlertLocations 1 param body → 200
POST
/alerts/{alertId}/locations/unlink
Tomorrow.io Unlink Alert Locations
unlinkAlertLocations 1 param body → 200
POST
/alerts/{alertId}/activate
Tomorrow.io Activate Alert
activateAlert 1 param → 200
POST
/alerts/{alertId}/deactivate
Tomorrow.io Deactivate Alert
deactivateAlert 1 param → 200

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Alert (8 properties), Location (6 properties), AlertCreateRequest (6 properties), Error (3 properties). Each schema is shown below with its type and property counts.

SimpleAck
object
Generic success acknowledgement.
2 properties
AlertLocationLinkRequest
object
1 property 1 required
Alert
object
A persistent alert that fires insights over linked locations and pushes activations to a webhook.
8 properties 3 required
AlertCreateRequest
object
Payload to create or update an alert.
6 properties 2 required
GeoJSONGeometry
object
GeoJSON geometry — Point, LineString, or Polygon.
2 properties 2 required
Location
object
A saved location resource.
6 properties 3 required
Error
object
Standard Tomorrow.io error envelope.
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tomorrow-alerts-api-openapi.yml Raw ↑

Other APIs Tomorrow.io publishes across the network.

Tomorrow.io Climate API
Tomorrow.io Events API
Tomorrow.io Forecast API
Tomorrow.io Historical API
Tomorrow.io Insights API
Tomorrow.io Locations API
Tomorrow.io Map Tiles API
Tomorrow.io Realtime API
Tomorrow.io Routes 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.