Particle Cloud API

Name: Particle Cloud API API
Brand: Particle Cloud API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIOTDevice Managementbearer12 EndpointsREST

For Agents

Control Particle IoT devices remotely — call device functions, read sensor variables, manage access tokens, and subscribe to real-time device events.

Quickstart

Get started with Particle Cloud 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:
"call a function on an IoT device"

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

Capabilities

What an agent can do with Particle Cloud API API.

Call remote functions on connected Particle devices and receive return values

Read real-time sensor variables from any online device in your fleet

Subscribe to server-sent event streams for device state changes and custom events

Publish events to all devices in a product fleet simultaneously

GET STARTED

Start building with Particle Cloud API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Particle Cloud API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Particle Cloud API, keeping it validated and agent-ready. Provision and control Particle IoT devices over the cloud, including calling remote functions, reading device variables, and streaming real-time events via SSE. The API handles access token lifecycle management with OAuth 2.0 and supports fleet-wide event publishing across 12 endpoints covering device interaction, event streaming, and authentication.

Use Cases

Patterns agents use Particle Cloud API API for, with concrete tasks.

★ AI Agent IoT Device Control

AI agents discover and invoke Particle device functions through Jentic's intent-based search without pre-configuring device IDs or function signatures. An agent searches for 'call a function on an IoT device', receives the POST /devices/{deviceId}/{functionName} schema, and executes the call with proper authentication handled by Jentic's credential vault. This pattern enables autonomous device control in smart factory, agriculture, and environmental monitoring scenarios.

Call the 'toggleRelay' function on device 0123456789abcdef with argument 'on' and verify the return value is 1

Real-Time Sensor Data Collection

Collect live sensor readings from deployed Particle devices by subscribing to server-sent event streams or polling device variables directly. The GET /events endpoint delivers real-time SSE streams filtered by event name, while GET /devices/{deviceId}/{functionName} returns the current value of any exposed variable. Supports fleet-wide monitoring across hundreds of devices with a single authenticated connection.

Read the 'humidity' variable from device abc123 and subscribe to the 'temperature' event stream to collect readings for 60 seconds

Fleet Event Broadcasting

Broadcast custom events to an entire fleet of Particle devices using the POST /events endpoint. Devices listen for named events and trigger firmware-defined handlers, enabling coordinated firmware updates, configuration changes, or emergency shutdown sequences across thousands of devices simultaneously without addressing each one individually.

Publish a 'config_update' event with data payload '{"interval": 30}' to trigger all fleet devices to update their reporting frequency

Access Token Lifecycle Management

Generate, list, and revoke OAuth access tokens for fine-grained API access control. The POST /oauth/token endpoint creates new tokens with configurable expiration, while DELETE /access_tokens/{token} enables immediate revocation for security incidents or credential rotation. Supports both user-level and product-level token scoping for multi-tenant IoT deployments.

Generate a new access token with 24-hour expiration using client credentials, then list all active tokens to confirm creation

Key Endpoints

12 endpoints — jentic publishes the only available openapi specification for particle cloud api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/devices/{deviceId}/{functionName}

Call a function on a Particle device

GET

/devices/{deviceId}/{functionName}

Read a variable from a device

GET

/devices

List all devices for the authenticated user

GET

/events

Subscribe to server-sent event stream

POST

/events

Publish an event to devices

POST

/oauth/token

Generate a new access token

POST

/devices/{deviceId}/wakeup

Wake a sleeping device

DELETE

/access_tokens/{token}

Revoke a specific access token

POST

/devices/{deviceId}/{functionName}

Call a function on a Particle device

GET

/devices/{deviceId}/{functionName}

Read a variable from a device

GET

/devices

List all devices for the authenticated user

GET

/events

Subscribe to server-sent event stream

POST

/events

Publish an event to devices

Why though Jentic?

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

Credential isolation

Particle OAuth tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped bearer tokens — raw client credentials never enter the agent's context window.

Intent-based discovery

Agents search by intent (e.g., 'call a function on an IoT device') and Jentic returns matching Particle operations with their input schemas, so the agent can invoke device functions without browsing Particle's documentation.

Time to first call

Direct Particle integration: 1-2 days for OAuth flow, SSE stream handling, and device addressing. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Balena Cloud API

Container-based fleet management for Linux single-board computers vs Particle's embedded MCU approach

Choose Balena when deploying containerized applications to Linux SBCs (Raspberry Pi, Jetson). Choose Particle for embedded MCU devices with constrained resources.

Alternative

Golioth API

SDK-first IoT platform for MCU devices with OTA updates and LightDB state storage

Choose Golioth when you need device-side SDK integration with Zephyr/ESP-IDF and LightDB state management. Choose Particle for a vertically integrated hardware+cloud platform.

Complementary

ThingsBoard API

Open-source IoT dashboard and rule engine for visualizing device telemetry

Use ThingsBoard alongside Particle when you need advanced dashboards, rule chains, or device telemetry visualization that goes beyond Particle's built-in console.

Complementary

Adafruit IO API

Simple IoT data logging and dashboard service for hobby and education projects

Use Adafruit IO when you need simple feed-based data logging and IFTTT-style triggers. Choose Particle for production-grade fleet management with OTA firmware updates.

FAQs

Specific to using Particle Cloud API API through Jentic.

Why is there no official OpenAPI spec for Particle Cloud API?

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

The Particle Cloud API uses Bearer token authentication. Tokens are obtained via the POST /oauth/token endpoint using client credentials (client_id and client_secret). Through Jentic, these credentials are stored in the encrypted MAXsystem vault and agents receive scoped tokens without handling raw secrets.

Can I call a function on a specific Particle device through this API?

Yes. Send a POST request to /devices/{deviceId}/{functionName} with optional arguments in the request body. The device executes the firmware-defined function and returns an integer result value. Functions must be registered in device firmware using Particle.function().

How do I stream real-time events from Particle devices through Jentic?

Use the GET /events endpoint which returns a server-sent event (SSE) stream. Through Jentic, search for 'subscribe to Particle device events' to get the operation schema, then execute with your event name filter. The stream delivers events as they occur with device ID, timestamp, and payload data.

What are the rate limits for the Particle Cloud API?

The Particle Cloud API enforces rate limits per access token. Device function calls and variable reads are limited to approximately 120 requests per minute per device. The event publishing endpoint allows roughly 1 event per second per device. SSE stream connections are limited to 4 concurrent connections per access token.

Can I wake a sleeping Particle device using this API?

Yes. The POST /devices/{deviceId}/wakeup endpoint sends a wake signal to mesh-network devices in sleep mode. This is useful for battery-powered sensors where you need an on-demand reading without waiting for the device's normal wake cycle.