Adafruit IO REST API

Name: Adafruit IO REST API API
Brand: Adafruit IO REST API
Availability: InStock

✓ Official Vendor SpecIOTSensor DataapiKey71 EndpointsREST

For Agents

Manage feeds, dashboards, triggers, tokens, ACLs, and webhooks across the full Adafruit IO REST surface for IoT projects.

Quickstart

Get started with Adafruit IO REST API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create an Adafruit IO trigger"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Adafruit IO REST API API.

Create feeds and ingest data points individually or in batches under /{username}/feeds and group-scoped /{username}/groups/{group_key}/feeds/{feed_key}/data/batch

Build IoT dashboards and add blocks via /{username}/dashboards and /{username}/dashboards/{dashboard_id}/blocks

Create triggers that fire automations on feed values via /{username}/triggers

Manage device tokens through /{username}/tokens and /{username}/tokens/{id}

GET STARTED

Start building with Adafruit IO REST API API

Explore with Jentic

View OpenAPI Spec

Adafruit IO is the cloud service paired with Adafruit's maker hardware, used to log sensor data, build dashboards, and trigger automations from connected devices. This REST API exposes feeds, dashboards, blocks, groups, triggers, tokens, ACL, throttle status, and webhook endpoints across 71 operations. Authentication uses the X-AIO-Key header (or query parameter) and an optional X-AIO-Signature for signed requests. The /{username}/groups/{group_key}/feeds/{feed_key}/data/batch path supports batched ingest scoped to a group, and the /{username}/triggers resource lets devices fire automations based on feed values.

Use Cases

Patterns agents use Adafruit IO REST API API for, with concrete tasks.

★ Trigger-based automations

Adafruit IO triggers fire when feed data crosses a threshold or matches a value, useful for hobbyist alerting (e.g. notify when humidity drops below 30%). An agent can POST to /{username}/triggers with the feed and condition, and pair the trigger output with an external notification API. This avoids polling feed values from a separate service.

POST a trigger to /{username}/triggers when the temp feed exceeds 30 and connect it to a notification webhook

Group-level batch ingest

Devices that publish multiple feeds (e.g. a weather station publishing temperature, humidity, and pressure together) can post a group-scoped batch via /{username}/groups/{group_key}/feeds/{feed_key}/data/batch. This lets the group's feeds stay in lockstep, which simplifies later analysis and dashboard rendering.

Post a 10-minute window of telemetry to /{username}/groups/weather/feeds/temp/data/batch and then to humidity

Token and ACL management for fleets

Operators of small device fleets issue per-device tokens and apply ACL rules so each device only reads or writes its own feed. /{username}/tokens manages token creation and rotation, while /{username}/{type}/{type_id}/acl applies access rules. An agent can rotate a compromised token and update ACL entries in a single workflow.

List tokens at /{username}/tokens, revoke the compromised id, create a new token, and update the ACL on the affected feed

Webhook telemetry capture

Some devices push data to Adafruit IO's webhook endpoints (e.g. /webhooks/feed/:token) rather than calling REST endpoints directly. An agent acting as the device's gateway can sign and forward payloads, and the /webhooks/feed/:token/raw variant handles non-JSON sensor payloads. This is helpful for legacy hardware or third-party trackers.

Forward a raw sensor payload to /webhooks/feed/<token>/raw and confirm the response status

AI agent integration

Makers building agent assistants for their lab or smart home expose Adafruit IO REST through Jentic alongside notification APIs. The X-AIO-Key (and signature, when used) lives in the Jentic vault, so the agent searches by intent — 'create a trigger', 'add a dashboard block' — without seeing raw keys.

Search Jentic for 'create an Adafruit IO trigger when temp exceeds 30', load the schema, and execute it

Key Endpoints

71 endpoints — adafruit io is the cloud service paired with adafruit's maker hardware, used to log sensor data, build dashboards, and trigger automations from connected devices.

METHOD

PATH

DESCRIPTION

POST

/{username}/feeds/{feed_key}/data/batch

Batch ingest data points

POST

/{username}/groups/{group_key}/feeds/{feed_key}/data/batch

Group-scoped batch ingest

POST

/{username}/triggers

Create a trigger

POST

/{username}/dashboards

Create a dashboard

POST

/{username}/dashboards/{dashboard_id}/blocks

Add a dashboard block

POST

/{username}/tokens

Create a device token

GET

/{username}/throttle

Read throttle status

GET

/{username}/feeds/{feed_key}/data/chart

Get chart-aggregated data

POST

/{username}/feeds/{feed_key}/data/batch

Batch ingest data points

POST

/{username}/groups/{group_key}/feeds/{feed_key}/data/batch

Group-scoped batch ingest

POST

/{username}/triggers

Create a trigger

POST

/{username}/dashboards

Create a dashboard

POST

/{username}/dashboards/{dashboard_id}/blocks

Add a dashboard block

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Adafruit IO X-AIO-Key and X-AIO-Signature values are stored encrypted in the Jentic vault. Agents receive scoped execution handles, so the raw key and signature never enter the agent's prompt context.

Intent-based discovery

Agents search Jentic by intent, e.g. 'create an Adafruit IO trigger' or 'rotate a device token', and Jentic returns the matching operation with its input schema.

Time to first call

Direct Adafruit IO REST integration: 1-2 days for auth, triggers, ACL, and dashboard plumbing. Through Jentic: under 1 hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Adafruit IO API

Slimmer 18-endpoint Adafruit IO surface — feeds, groups, and user only.

Use the slimmer Adafruit IO API when you only need feeds and groups; this surface adds triggers, tokens, ACL, and dashboards.

Alternative

Particle API

End-to-end IoT platform with hardware, cellular SIM, and OTA firmware updates.

Choose Particle when the project needs OTA firmware management and SIM connectivity, which Adafruit IO does not provide.

Alternative

Blynk API

Mobile-first IoT platform with a drag-and-drop dashboard builder.

Pick Blynk when end users interact mainly via a mobile app rather than the Adafruit IO web UI.

FAQs

Specific to using Adafruit IO REST API API through Jentic.

What authentication does the Adafruit IO REST API use?

The API supports an X-AIO-Key API key, in either the request header or query string, and an X-AIO-Signature header for signed requests. Through Jentic, both values are stored encrypted in the Jentic vault and the agent receives a scoped execution handle, so the raw key and signature never appear in prompts.

Can I create triggers and tokens with the Adafruit IO REST API?

Yes. POST /{username}/triggers creates a feed-value trigger, and POST /{username}/tokens issues a per-device token. Both are useful for fleet deployments where each device needs its own credentials and event automations bound to specific feeds.

What are the rate limits for the Adafruit IO REST API?

Adafruit IO enforces a per-minute throughput cap that depends on the account tier. Use GET /{username}/throttle to read your current remaining capacity, and prefer batch ingest via /{username}/feeds/{feed_key}/data/batch or /{username}/groups/{group_key}/feeds/{feed_key}/data/batch over single-point posts.

How do I create a trigger when a feed crosses a threshold through Jentic?

Run pip install jentic, search Jentic for 'create an Adafruit IO trigger', load the schema for POST /{username}/triggers, and execute it with the feed_key, condition, and threshold value. Jentic injects the X-AIO-Key from the vault.

Does the Adafruit IO REST API support access control on feeds?

Yes. The /{username}/{type}/{type_id}/acl and /{username}/{type}/{type_id}/acl/{id} endpoints manage access control rules per resource. That lets you keep a feed writable by one device token but read-only for another or for collaborators.

Can devices push telemetry to Adafruit IO via webhooks?

Yes. /webhooks/feed/:token accepts JSON payloads and /webhooks/feed/:token/raw accepts arbitrary raw payloads, which is useful for legacy hardware or third-party trackers that cannot be easily reconfigured to call the REST endpoints directly.