How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Particle

Particle Devices API

The Devices API from Particle — 9 operation(s) for devices.

Documentation Provider Profile APIs.io OpenAPI GitHub

Particle Devices API is one of 25 APIs that Particle publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Devices. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a getting-started guide.

This API exposes 11 operations across 9 paths. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against a single base URL, https://api.particle.io.

11 operations 9 paths 0 schemas 1 DELETE7 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://api.particle.io
Authentication
HTTP Bearer
Contact
Particle Developer Support
License
Apache 2.0
Resource Areas
1

Authentication & Security 1

Particle Devices API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — OAuth 2.0 bearer token. Obtain via POST /oauth/token.

Paths & Operations 11

Across 9 paths, the API surfaces 11 operations — 1 DELETE, 7 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Devices 11
POST
/v1/devices
Claim a device
ClaimDevice → 200400401
GET
/v1/devices
List devices
ListDevices → 200400401
GET
/v1/products/{productIdOrSlug}/devices/{deviceId}
Get product device information
GetProductDevice 2 params → 200400401
DELETE
/v1/devices/{deviceId}
Unclaim device
unclaimDevice 1 param → 200400401
GET
/v1/devices/{deviceId}
Get device information
GetDevice 1 param → 200400401
GET
/v1/serial_numbers/{serial_number}
Look up device identification from a serial number
GetV1Serial_numbersSerial_number 1 param → 200400401
GET
/v1/products/{productIdOrSlug}/devices
List devices in a product
listDevicesForProduct 1 param → 200400401
GET
/v1/products/{productIdOrSlug}/device_orders
List device orders for a product
listDeviceOrdersForProduct 1 param → 200400401
GET
/v1/devices/{deviceId}/{varName}
Get a variable value
GetDeviceVariable 2 params → 200400401
POST
/v1/devices/{deviceId}/{functionName}
Call a function
PostV1DevicesDeviceidFunctionname 2 params → 200400401
PUT
/v1/devices/{deviceId}/ping
Ping a device
PutV1DevicesDeviceidPing 1 param → 200400401

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

particle-devices-api-openapi.yml Raw ↑

Other APIs Particle publishes across the network.

Particle Authentication API
AE Profile APIs.io
Particle Configuration API
AE Profile APIs.io
Particle Customers API
AE Profile APIs.io
Particle Diagnostics API
AE Profile APIs.io
Particle Env API
AE Profile APIs.io
Particle Events API
AE Profile APIs.io
Particle Firmware API
AE Profile APIs.io
Particle FleetHealth API
AE Profile APIs.io
Particle Groups API
AE Profile APIs.io
Particle Integrations API
AE Profile APIs.io
Particle Ledger API
AE Profile APIs.io
Particle Location API
AE Profile APIs.io
#Devices
← Back to P APIs
API Details
ID
particle:particle-devices-api
Base URL
https://api.particle.io
Docs
https://docs.particle.io/reference/cloud-apis/api/
Provider
Particle
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=particle-devices-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/particle-devices-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Particle Devices API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.