Adafruit IO API

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

★ Only Publicly Available SpecIOTSensor DataapiKey13 EndpointsREST

For Agents

Read and publish IoT sensor data to Adafruit IO feeds and groups so an agent can ingest telemetry or react to live device readings.

Quickstart

Get started with Adafruit IO 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 API API.

Publish a single sensor reading or batch of readings to an Adafruit IO feed

Retrieve the latest data point from a named feed for dashboards or alerts

Create new feeds on demand when a device first reports data

Group multiple feeds together and publish coordinated updates in one call

GET STARTED

Start building with Adafruit IO API API

Explore with Jentic

View OpenAPI Spec

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

Jentic publishes the only available OpenAPI specification for Adafruit IO API, keeping it validated and agent-ready. Adafruit IO is a hosted IoT data platform that lets makers and small fleets push sensor readings into named feeds, group feeds together, and read history back for dashboards or downstream automation. This compact 13-endpoint surface focuses on the core data path: list and create feeds, publish single or batch data points, fetch the last reading, chart historical data, and group feed updates into one call.

Use Cases

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

★ Maker Sensor Telemetry

Hobbyists and classroom projects can stream readings from microcontrollers such as the Adafruit Feather or Raspberry Pi straight into named feeds, then read the latest value from a phone or web client. The 13-endpoint surface keeps the integration small enough for an embedded device while supporting batch uploads when connectivity is intermittent.

Publish a temperature reading of 22.4 to the 'living-room-temp' feed and confirm the response status was created.

Live Dashboard Backing Data

Web dashboards can call the last data point and chart endpoints to render real-time tiles for a small fleet of devices. Adafruit IO holds the time-series, so the dashboard does not need its own storage layer and refreshes are a single GET per feed.

Fetch the most recent value from the 'pressure' feed and pull the last 60 minutes of chart data for rendering a sparkline.

Grouped Multi-Sensor Publishing

Devices that produce several correlated readings (temperature, humidity, light) can publish them as a single grouped update so the readings share a timestamp. The /groups/{group_key}/data endpoint accepts an array of feed updates in one round trip, which matters when devices run on a battery or limited cellular plan.

Publish a grouped update with temperature 21.0, humidity 55, and light 320 to the 'greenhouse' group in a single call.

Agent-Driven IoT Monitoring

An AI agent connected via Jentic can poll the last data point on a watchlist of feeds, detect when a reading crosses a threshold, and trigger a downstream alert. The agent uses Jentic to search Adafruit IO operations by intent rather than wiring the X-AIO-Key header by hand.

Read the last value from each feed in the 'fridge-monitor' group and raise an alert if the temperature feed exceeds 5.0.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/{username}/feeds

List all feeds

POST

/{username}/feeds

Create a new feed

GET

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

Get all data for a feed

POST

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

Publish a data point

POST

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

Publish a batch of data points

GET

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

Get the last data point

POST

/{username}/groups/{group_key}/data

Publish grouped data across feeds

GET

/{username}/feeds

List all feeds

POST

/{username}/feeds

Create a new feed

GET

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

Get all data for a feed

POST

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

Publish a data point

POST

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

Publish a batch of data points

Why though Jentic?

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

Credential isolation

The Adafruit IO X-AIO-Key is stored encrypted in the Jentic vault. Agents receive a scoped reference and the header is injected at execution time, so the raw key never appears in agent prompts or logs.

Intent-based discovery

Agents search Jentic by intent ('publish sensor data', 'read last value') and Jentic returns the matching Adafruit IO feed or data operation with its input schema.

Time to first call

Direct Adafruit IO integration: a few hours to wire auth, feed creation, and error handling. Through Jentic: under 30 minutes for the search, load, execute loop.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Adafruit IO REST API

The full Adafruit IO REST surface with 71 endpoints covering activities, dashboards, blocks, and more.

Use the full REST API when you need dashboards, blocks, throttle info, or activity history; use this compact 13-endpoint variant for the core feed/data path only.

Alternative

Particle Cloud

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

Choose Particle when the user needs device firmware management and cellular SIMs; choose Adafruit IO for hobby telemetry on existing Wi-Fi devices.

Complementary

Zapier NLA

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

Use Zapier alongside Adafruit IO when the user wants reaction to feed thresholds wired into existing Zapier workflows.

FAQs

Specific to using Adafruit IO API API through Jentic.

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

Adafruit does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Adafruit IO 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 API use?

Adafruit IO uses an API key sent in the X-AIO-Key header on every request. Through Jentic the key is stored encrypted in the vault and injected at execution time so the raw key never enters the agent context.

Can I publish a sensor reading through the Adafruit IO API?

Yes. POST to /{username}/feeds/{feed_key}/data with a JSON body containing the value, or POST to /{username}/feeds/{feed_key}/data/batch to send several readings in one request. The response includes the assigned id and created_at timestamp.

What are the rate limits for the Adafruit IO API?

Free accounts allow 30 data modifications per minute and IO+ accounts allow 60 per minute. Read calls count more leniently; use the batch data endpoint when publishing many readings at once to stay under the limit.

How do I publish a reading to a feed with Jentic?

Search Jentic for 'publish a sensor reading to Adafruit IO', load the schema for POST /{username}/feeds/{feed_key}/data, and execute with the value. The flow is: pip install jentic, then await client.search, await client.load, await client.execute.

Can I read the latest value from a feed?

Yes. GET /{username}/feeds/{feed_key}/data/last returns the most recent data point for the feed including the value and created_at timestamp, which is useful for live dashboards and threshold alerts.