Adafruit IO REST API

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

★ Only Publicly Available OpenAPI DocumentIOTSensor DataapiKey71 EndpointsREST

Install Jentic One Beta

Connect the Adafruit IO REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adafruit IO REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Adafruit IO REST API.

Create and manage feeds, including batch ingest, chart data, and last/first/next/previous data points under /{username}/feeds

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

Inspect feed throughput limits using /{username}/throttle

GET STARTED

Start building with Adafruit IO REST API

Explore with Jentic

View OpenAPI Document

For Agents

Manage feeds, dashboards, blocks, and signed requests across the full Adafruit IO REST surface for IoT projects.

Use for: I need to create a new Adafruit IO dashboard, Add a chart block to an existing dashboard, Pull chart-aggregated data for a feed over the last 24 hours, Check how close I am to the Adafruit IO throttle limit

Not supported: Does not handle device firmware OTA, cellular connectivity, or paid IoT SIMs — use for Adafruit IO feeds, dashboards, blocks, throttle, and activity data only.

Jentic publishes the only available OpenAPI specification for Adafruit IO REST API, keeping it validated and agent-ready. The Adafruit IO REST API exposes the full IoT platform surface — feeds, dashboards and blocks, groups, throttle status, activities, charts, and signed-request authentication. The spec covers 71 endpoints and supports both header and query API key auth (X-AIO-Key) plus an X-AIO-Signature scheme for signed requests. Endpoints under /{username}/feeds include chart, batch, retain, previous, next, first, and last data accessors for finely controlled telemetry retrieval.

Use Cases

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

★ Dashboard automation

Makers and educators auto-provision Adafruit IO dashboards for student projects or home setups. An agent can POST to /{username}/dashboards to create the dashboard, then POST to /{username}/dashboards/{dashboard_id}/blocks for each chart, gauge, or toggle block. This avoids dragging blocks around the UI for every new project.

Create a dashboard 'classroom-temp', then add chart blocks for the temperature, humidity, and pressure feeds via /{username}/dashboards/{dashboard_id}/blocks

Time-series chart retrieval

Analytics workflows need pre-aggregated chart data instead of raw points. /{username}/feeds/{feed_key}/data/chart returns chartable summaries that suit dashboards and ML feature pipelines without client-side bucketing. An agent can pull the chart series, then push it into a notebook or warehouse.

GET /{username}/feeds/temp/data/chart with hours=24 and resolution=15 minutes, then export to a Parquet file

Throttle-aware ingest

Devices that send frequent telemetry can exhaust Adafruit IO's per-minute limits. An agent can periodically GET /{username}/throttle to read remaining capacity, then decide whether to batch via /{username}/feeds/{feed_key}/data/batch or pause ingest. This makes the device cooperative with the platform's fair-use limits.

GET /{username}/throttle, and if remaining is low, batch the next 5 minutes of readings via /{username}/feeds/{feed_key}/data/batch

Signed-request device auth

Some constrained devices cannot safely store a long-lived API key. Adafruit IO supports signed requests using the X-AIO-Signature header alongside an X-AIO-Key, so a backend can pre-sign a request that a device executes within a short window. An agent can act as the signing service for a fleet of devices.

Generate an X-AIO-Signature for a POST to /{username}/feeds/temp/data and hand it to the device for execution

AI agent integration

Makers building agent assistants for their lab or home expose Adafruit IO REST through Jentic alongside notification and dashboarding APIs. The X-AIO-Key (and signature where used) live in the Jentic vault; the agent searches by intent — 'create a dashboard', 'read a chart', 'check throttle' — without seeing raw keys.

Search Jentic for 'create an Adafruit IO dashboard with charts', load the dashboard and block schemas, and execute them in sequence

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

/{username}/feeds

List feeds

POST

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

Batch ingest data points

GET

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

Get chart-aggregated feed data

GET

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

Get the latest data point

POST

/{username}/dashboards

Create a dashboard

POST

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

Add a block to a dashboard

GET

/{username}/throttle

Read throttle status

GET

/{username}/activities

List recent activities

GET

/{username}/feeds

List feeds

POST

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

Batch ingest data points

GET

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

Get chart-aggregated feed data

GET

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

Get the latest data point

POST

/{username}/dashboards

Create a dashboard

Why 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 neither value appears in prompts or logs.

Intent-based discovery

Agents search Jentic by intent, e.g. 'create an Adafruit IO dashboard' or 'check throttle status', and Jentic returns the matching operation with its input schema.

Time to first call

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

FAQs

Specific to using Adafruit IO REST API through Jentic.

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

Adafruit publishes API documentation but not a structured 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?

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 dashboards and blocks with the Adafruit IO REST API?

Yes. POST /{username}/dashboards creates a dashboard, and POST /{username}/dashboards/{dashboard_id}/blocks adds chart, gauge, or toggle blocks tied to specific feeds. The full block lifecycle (create, update, delete) is exposed under /{username}/dashboards/{dashboard_id}/blocks/{id}.

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 over single-point posts to stay within budget.

How do I create an Adafruit IO dashboard through Jentic?

Run pip install jentic, search Jentic for 'create an Adafruit IO dashboard', load the schema for POST /{username}/dashboards, and execute it with a name. Then chain a search for 'add a block to an Adafruit IO dashboard' to load POST /{username}/dashboards/{dashboard_id}/blocks. Jentic injects the X-AIO-Key from the vault.

Does the Adafruit IO REST API support data retention rules?

Yes. The /{username}/feeds/{feed_key}/data/retain endpoint configures retention behaviour for a feed — useful when you want long-term storage for some feeds but not others, or when you need to cap storage for a constrained tier.

Adafruit IO REST API

Connect the Adafruit IO REST API to your agent

Capabilities

Start building with Adafruit IO REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs