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

OpenAQ Locations API

The Locations API from OpenAQ — 11 operation(s) for locations.

OpenAQ Locations API is one of 28 APIs that OpenAQ 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 and API documentation.

This API exposes 11 operations across 11 paths, and defines 47 schemas. It is described by OpenAPI 3.1.0, at version 2.0.0.

Requests are made against the base URL http://api.example.com.

11 operations 11 paths 47 schemas 11 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2.0.0
Base URL
http://api.example.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

OpenAQ Locations API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-API-Key (APIKeyHeader).

Paths & Operations 11

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

Locations 11
GET
/v3/locations/{locations_id}
OpenAQ Get a location by ID
location_get_v3_locations__locations_id__get 1 param → 200422
GET
/v3/locations
OpenAQ Get locations
locations_get_v3_locations_get 17 params → 200422
GET
/v3/locations/{locations_id}/sensors
OpenAQ Get sensors by location ID
sensors_get_v3_locations__locations_id__sensors_get 1 param → 200422
GET
/v3/locations/{locations_id}/latest
OpenAQ Get a location's latest measurements
location_latest_get_v3_locations__locations_id__latest_get 4 params → 200422
GET
/v3/locations/{locations_id}/flags
OpenAQ Get flags by location ID
location_flags_get_v3_locations__locations_id__flags_get 5 params → 200422
GET
/v2/locations/{location_id}deprecated
OpenAQ Get a location by ID
get_v2_location_by_id_v2_locations__location_id__get 5 params → 200422
GET
/v2/locationsdeprecated
OpenAQ Get locations
locations_get_v2_locations_get 23 params → 200422
GET
/v2/latest/{location_id}deprecated
OpenAQ Get latest measurements by location ID
get_v2_latest_by_id_v2_latest__location_id__get 5 params → 200422
GET
/v1/latest/{location_id}deprecated
OpenAQ Get latest measurements by location ID
get_v1_latest_by_id_v1_latest__location_id__get 5 params → 200422
GET
/v1/locations/{location_id}deprecated
OpenAQ Get location by ID
get_v1_locations_by_id_v1_locations__location_id__get 5 params → 200422
GET
/v1/locationsdeprecated
OpenAQ Get locations
locationsv1_get_v1_locations_get 23 params → 200422

Schemas 47

The contract defines 47 schemas that model the data the API accepts and returns. The most detailed are Location (17 properties), LocationsRow (16 properties), LocationsRowV1 (16 properties), openaq_api__models__responses__Parameter (11 properties). Each schema is shown below with its type and property counts.

Sort
string
LatestResponseV1
object
2 properties 1 required
EntityTypes
string
openaq_api__models__responses__Manufacturer
object
2 properties 2 required
LatestRowV1
object
5 properties 3 required
Latest
object
5 properties 5 required
LocationFlag
object
6 properties 4 required
LocationLicense
object
5 properties 3 required
ProviderBase
object
2 properties 2 required
Source
object
6 properties 1 required
openaq_api__models__responses__Parameter
object
11 properties 8 required
AttributionEntity
object
2 properties 1 required
Location
object
17 properties 11 required
FlagType
object
3 properties 3 required
EntityBase
object
2 properties 2 required
CountsByMeasurementItem
object
2 properties 2 required
LatestMeasurementRow
object
6 properties 6 required
Sensor
object
8 properties 3 required
Coordinates
object
2 properties
LocationsRow
object
16 properties 3 required
Summary
object
9 properties
ParameterBase
object
4 properties 3 required
InstrumentBase
object
2 properties 2 required
LatestRow
object
5 properties 1 required
openaq_api__v3__models__responses__Meta
object
5 properties
LatestMeasurement
object
4 properties 4 required
LocationsSortFields
string
SensorBase
object
3 properties 3 required
DatetimeObject
object
2 properties 2 required
LocationFlagsResponse
object
2 properties 1 required
openaq_api__v3__models__responses__LatestResponse
object
2 properties 1 required
openaq_api__models__responses__LocationsResponse
object
2 properties 1 required
LocationsRowV1
object
16 properties 14 required
openaq_api__models__responses__LatestResponse
object
2 properties 1 required
ValidationError
object
3 properties 3 required
SensorsResponse
object
2 properties 1 required
HTTPValidationError
object
1 property
AveragingPeriodV1
object
2 properties 1 required
Coverage
object
8 properties 6 required
CountryBase
object
3 properties 2 required
SensorTypes
string
openaq_api__models__responses__Meta
object
6 properties
LocationsResponseV1
object
2 properties 1 required
LatestBase
object
3 properties 3 required
openaq_api__v3__models__responses__LocationsResponse
object
2 properties 1 required
LocationsOrder
string
SortOrder
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openaq-locations-api-openapi.yml Raw ↑

Other APIs OpenAQ publishes across the network.

OpenAQ Averages API
OpenAQ Cities API
OpenAQ Countries API
OpenAQ Daily API
OpenAQ Days API
OpenAQ Flags API
OpenAQ Hourly API
OpenAQ Hours API
OpenAQ Instruments API
OpenAQ Latest API
OpenAQ Licenses API
OpenAQ Manufacturers API
Where this information came from

This is an independent, third-party profile of OpenAQ 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.