Flash new firmware to a Particle device over-the-air via the Cloud API

domain: iot · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Compile your application firmware to a binary (.bin) with the Particle CLI (particle compile) or Workbench, or let the flash command compile it for you
  2. For a claimed device, run particle flash <device> <path> (CLI), or use Workbench's Cloud Flash / Web IDE's Flash button, which use the Cloud API under the hood
  3. To flash directly via REST, send PUT https://api.particle.io/v1/devices/:deviceId (or the product form /v1/products/:productIdOrSlug/devices/:deviceId) as multipart form data with file=@firmware.bin and file_type=binary plus a bearer access token
  4. If the device belongs to a product, mark it as a development device first, otherwise the cloud immediately re-flashes it with the released product firmware after your manual update
  5. If OTA updates were disabled on-device via System.disableUpdates(), force them via PUT /v1/products/:productId/devices/:deviceId with firmware_updates_forced: true

Known gotchas

Related routes

Publish and subscribe to device events using the Particle Device Cloud API and webhooks
docs.particle.io · 6 steps · unrated
Set up an over-the-air firmware update pipeline for an ESPHome device
esphome.io · 6 steps · unrated
Perform an OTA firmware update to an ESPHome device via the native API OTA platform
iot · 5 steps · unrated

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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans