Automate OpenAQ

What OpenAQ is

API for OpenAQ LCS

API host: openaq.local

What HumDay can read from OpenAQ

These are the operations a schedule or a trigger can watch.

• GETPong/ping
• GETProvides a simple listing of cities within the platform/v1/cities
• GETLatest V1 Get/v1/latest
• GETProvides a simple listing of cities within the platform/v2/cities
• GETLatest Get/v2/latest
• GETModel Get/v2/models
• GETSources V1 Get/v1/sources
• GETSources Get/v2/sources
• GETSummary Get/v2/summary
• GETFavico/favicon.ico
• GETAverages V2 Get/v2/averages
• GETProjects Get/v2/projects
• GETCountries Getv1/v1/countries
• GETLocationsv1 Get/v1/locations
• GETCountries Get/v2/countries
• GETLocations Get/v2/locations
• GETParameters Getv1/v1/parameters
• GETParameters Get/v2/parameters
• GETMeasurements Get V1/v1/measurements
• GETMeasurements Get/v2/measurements
• GETMfr Get/v2/manufacturers
• GETLatest V1 Get/v1/latest/{location_id}
• GETLatest Get/v2/latest/{location_id}
• GETProjects Get/v2/projects/{project_id}
• GETCountries Get/v1/countries/{country_id}
• GETCountries Get/v2/countries/{country_id}
• GETLocationsv1 Get/v1/locations/{location_id}
• GETLocations Get/v2/locations/{location_id}
• GETDemo/v2/locations/tiles/viewer
• GETReadme Get/v2/sources/readme/{slug}
• GETTilejson/v2/locations/tiles/tiles.json
• GETMobiletilejson/v2/locations/tiles/mobile/tiles.json
• GETMobilegentilejson/v2/locations/tiles/mobile-generalized/tiles.json
• GETGet Tile/v2/locations/tiles/{z}/{x}/{y}.pbf
• GETGet Mobiletile/v2/locations/tiles/mobile/{z}/{x}/{y}.pbf
• GETGet Mobilegentile/v2/locations/tiles/mobile-generalized/{z}/{x}/{y}.pbf

How automating OpenAQ works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live OpenAQ account.
4. Grant access, then go live. You approve the specific OpenAQ operations it may use — and only those.

Automate OpenAQ with these

• HERE Tracking205 operations
• Traccar61 operations
• eDRV57 operations
• uebermaps endpoints56 operations
• Google My Business50 operations
• Weatherbit Interactive Swagger UI Documentation47 operations
• Waterlinked The Water Linked Underwater GPS38 operations
• Enode28 operations
• Neutrinoapi Neutrino27 operations
• Staging Ecotaco .ecota.co27 operations
• Viator Documentation & Specification Merchant Partners27 operations
• Mashape GeoDB Cities26 operations

Categories

• Location

Questions about OpenAQ automation

Can HumDay connect to OpenAQ?

Yes. HumDay reads OpenAQ's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 36 operations are documented.

Do I need to write code to automate OpenAQ?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your OpenAQ account.

What can HumDay do in OpenAQ?

0 of the 36 documented operations change something in OpenAQ, and 36 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my OpenAQ account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to OpenAQ is held behind that approval.

Where this came from

The operations above are read from a published API description for OpenAQ at docs.openaq.org/openapi.json. Descriptions are the provider’s own words, not ours. Last published 2021-08-23.