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

CRUD over monitored point / polygon / polyline locations with tags.

Tomorrow.io Locations 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 Locations. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and code examples.

This API exposes 7 operations across 4 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.

7 operations 4 paths 7 schemas 1 DELETE2 GET3 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 Locations 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 7

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

Locations 7

CRUD over monitored point / polygon / polyline locations with tags.

GET
/locations
Tomorrow.io List Locations
listLocations → 200401429
POST
/locations
Tomorrow.io Create Location
createLocation body → 201400401429
GET
/locations/{locationId}
Tomorrow.io Get Location
getLocation 1 param → 200401404429
PUT
/locations/{locationId}
Tomorrow.io Update Location
updateLocation 1 param body → 200400401404429
DELETE
/locations/{locationId}
Tomorrow.io Delete Location
deleteLocation 1 param → 204401404429
POST
/locations/tags/add
Tomorrow.io Add Location Tags
addLocationTags body → 200400401429
POST
/locations/tags/remove
Tomorrow.io Remove Location Tags
removeLocationTags body → 200400401429

Schemas 7

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

SimpleAck
object
Generic success acknowledgement.
2 properties
GeoJSONGeometry
object
GeoJSON geometry — Point, LineString, or Polygon.
2 properties 2 required
Error
object
Standard Tomorrow.io error envelope.
3 properties 3 required
Location
object
A saved location resource.
6 properties 3 required
LocationTagsRequest
object
Payload for bulk add/remove of tags across locations.
2 properties 2 required
LocationUpdateRequest
object
Payload to update a saved location.
3 properties
LocationCreateRequest
object
Payload to create a new saved location.
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tomorrow-locations-api-openapi.yml Raw ↑

Other APIs Tomorrow.io publishes across the network.

Tomorrow.io Alerts API
Tomorrow.io Climate API
Tomorrow.io Events API
Tomorrow.io Forecast API
Tomorrow.io Historical API
Tomorrow.io Insights 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 Locations 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.