Call a Particle device's exposed cloud function and read one of its cloud variables from a backend service
domain: docs.particle.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain an access_token for the Particle account (or a scoped device access token)
Call a Particle.function() by POSTing to /v1/devices/{deviceId}/{functionName} with the argument in the request body and an Authorization: Bearer <access_token> header
Read a Particle.variable() by GETing /v1/devices/{deviceId}/{variableName}, optionally with ?format=raw for the raw value
Set up a Particle Integration (webhook) to forward Particle.publish() events to an external URL
Confirm webhook delivery by watching for the device's hook-sent event in its event stream
Known gotchas
POST/PUT calls should use the access_token in the Authorization header -- query-string access_token works for GET but is not reliable for function calls in all client setups
function calls fail if the device is offline at call time; there is no queuing/retry built into the basic function-call endpoint
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?