create a purpleair sensor group to poll multiple sensors and read their data in one call
domain: api.purpleair.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Request an API key pair from PurpleAir — a READ key for reading data and a WRITE key for creating/modifying resources
POST to /v1/groups with the WRITE key and a group name to create a group; the response returns a group_id
POST to /v1/groups/{group_id}/members with the WRITE key and a sensor_index to add each sensor as a group member
GET /v1/groups/{group_id}/members with the READ key and a fields query param (comma-separated field names) to read current data for all member sensors in one call
Use the group member-history endpoint to retrieve historical data for a specific member sensor within the group
Known gotchas
READ and WRITE keys are distinct — creating/deleting groups or members requires a WRITE key; data reads use a READ key
Groups exist specifically so you can poll many sensors in one request instead of hitting single-sensor endpoints repeatedly
The fields param must be set explicitly on member reads or the response may omit the measurements you need
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?