Adafruit IO REST API

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

★ Only Publicly Available SpecIOTDevice ManagementapiKey71 EndpointsREST

For Agents

Manage feeds, dashboards, groups, and devices on Adafruit IO so an agent can ingest telemetry, render dashboards, and orchestrate small fleets.

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:
"publish a sensor reading to Adafruit IO"

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

Capabilities

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

Publish single or batched sensor readings into named Adafruit IO feeds

Build and update dashboards with text, gauge, line chart, and slider blocks

Inspect account throttle status and recent activity history for diagnostics

Group feeds together and publish coordinated readings across them

GET STARTED

Start building with Adafruit IO REST API API

Explore with Jentic

View OpenAPI Spec

Use for: I need to publish a sensor reading to a feed, Get my current rate-limit consumption from Adafruit IO, List all dashboards on the account, Create a new gauge block on the greenhouse dashboard

Not supported: Does not handle device firmware updates, cellular connectivity, or general home-automation device control — use for Adafruit IO feeds, dashboards, groups, and triggers only.

Jentic publishes the only available OpenAPI specification for Adafruit IO REST API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Adafruit IO REST API, keeping it validated and agent-ready. Adafruit IO is a hosted IoT platform built around named feeds, dashboards, blocks, and groups, and the full REST surface exposes 71 endpoints covering account info, throttle and activity inspection, feed and data operations, dashboard layout, and webhook-style triggers. It is the broadest programmatic surface on the platform and pairs with hobbyist hardware such as the Feather, QT Py, and Raspberry Pi over HTTP or MQTT.

Use Cases

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

★ Hobbyist Dashboard Build-Out

Makers building a home dashboard can use the dashboards and blocks endpoints to lay out gauge, line-chart, and toggle blocks for each feed, then push live readings from the device. The 71-endpoint surface covers both the dashboard layout and the feed data, so a single integration handles read and render.

Create a dashboard called 'greenhouse', add a gauge block bound to the 'humidity' feed, and add a line-chart block bound to the 'temperature' feed.

Fleet Telemetry Ingest

Small device fleets in classrooms or workshops can push readings into per-device feeds, organise them with groups, and expose throttle and activity endpoints to monitor whether each device is reporting on schedule. Operators can spot a silent device by reading the activities endpoint instead of polling each feed.

List all feeds in the 'workshop' group, fetch the last data point on each, and report any feed with no reading in the last 30 minutes.

Threshold-Triggered Alerts

The triggers endpoints let operators set up reactive alerts when a feed value crosses a threshold or changes state, which is useful for fridge temperature monitoring, leak detection, or door sensors. The trigger fires server-side, so the device or agent does not need to poll continuously.

Create a trigger that fires when the 'fridge-temp' feed value rises above 5.0 and notify the configured webhook.

Agent-Driven IoT Orchestration

An AI agent connected via Jentic can read account-level throttle, locate feeds across groups, fan out data publishes, and add or remove dashboard blocks on demand. Jentic returns the right operation from the 71-endpoint spec by intent so the agent does not have to keep the path layout in context.

Read the throttle endpoint, then fan out one publish per feed in the 'workshop' group with the readings supplied by the user.

Key Endpoints

71 endpoints — jentic publishes the only available openapi specification for adafruit io rest api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/user

Get information about the current user

GET

/{username}/throttle

Get rate-limit consumption

GET

/{username}/feeds

List feeds for the user

POST

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

Publish a data point

GET

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

Get charted data for a feed

GET

/{username}/dashboards

List dashboards

GET

/{username}/activities

List recent activities

GET

/user

Get information about the current user

GET

/{username}/throttle

Get rate-limit consumption

GET

/{username}/feeds

List feeds for the user

POST

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

Publish a data point

GET

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

Get charted data for a feed

Why though Jentic?

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

Credential isolation

The X-AIO-Key is stored encrypted in the Jentic vault and never appears in agent prompts. Jentic injects the header at execution time, so even agents with weak prompt hygiene cannot leak the key.

Intent-based discovery

Agents search by intent ('build a dashboard', 'set a trigger', 'publish a reading') and Jentic returns the matching Adafruit IO operation with its input schema, so agents do not have to memorise 71 paths.

Time to first call

Direct integration of the full Adafruit IO REST API: 1-2 days for auth, dashboards, triggers, and error handling. Through Jentic: under an hour for the core flows.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Adafruit IO API

A compact 13-endpoint variant of the Adafruit IO API focused on feeds and data only.

Use this REST variant when you need dashboards, triggers, blocks, or activity history; use the compact variant when only feeds and data are required.

Alternative

Particle Cloud

Particle is a managed IoT platform with cellular SIMs and OTA firmware in addition to telemetry.

Choose Particle when the user needs device firmware updates or cellular fleet management; choose Adafruit IO for hobbyist Wi-Fi devices and dashboards.

Complementary

Zapier NLA

Zapier can react to Adafruit IO triggers and chain downstream actions such as notifications or sheet updates.

Use Zapier to wire reactions to Adafruit IO triggers without writing the alert delivery logic in code.

FAQs

Specific to using Adafruit IO REST API API through Jentic.

Why is there no official OpenAPI spec for Adafruit IO REST API?

Adafruit does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Adafruit IO REST API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Adafruit IO REST API use?

It accepts the API key in three ways: the X-AIO-Key header (HeaderKey), the X-AIO-Key query parameter (QueryKey), or an X-AIO-Signature header for signed requests. The header form is recommended; through Jentic the key is held in the encrypted vault and injected at execution time.

Can I check my rate-limit consumption through the API?

Yes. GET /{username}/throttle returns the current data rate limit and recent activity level for the authenticated user, which lets an agent decide whether to batch publishes or back off before hitting the per-minute cap.

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

Free accounts allow 30 data modifications per minute and IO+ accounts allow 60 per minute. Use the data/batch endpoint when publishing several readings in the same call to stay under the cap.

How do I add a block to a dashboard with Jentic?

Search Jentic for 'add a block to an Adafruit IO dashboard', load the schema for POST /{username}/dashboards/{dashboard_id}/blocks, and execute with the block type and feed binding. Run pip install jentic, then await client.search, await client.load, await client.execute.

Can I delete all activities for an account?

Yes. DELETE /{username}/activities clears the recorded activity log for the current user, which is useful when rebuilding a clean monitoring baseline.