Particle

The REST API covers devices (list, status, function calls, variable reads), events (publish and subscribe), firmware (OTA update management), products (fleet grouping), and webhooks (event forwarding to external services). Agents can call a function running on a device (like toggling a relay), read a published variable (like current temperature), trigger an OTA firmware update to a device group, and subscribe to the device event stream for real-time telemetry.

Reliability is production-grade for a managed IoT cloud platform. Particle handles the messaging infrastructure, device authentication, and OTA update delivery reliability. The event streaming infrastructure is designed for the sporadic, high-volume nature of IoT telemetry data. Teams managing large device fleets should use the fleet management APIs rather than per-device operations for efficiency.

Particle is an IoT device platform providing the cloud infrastructure for connected hardware — device registry, OTA firmware updates, telemetry ingestion, event streaming, and fleet management through a REST API. For agents managing connected device products, Particle's cloud API enables programmatic device management operations: querying device status, pushing firmware updates, reading sensor telemetry, and triggering device functions remotely. The platform supports both prototyping and production fleet scales.

Authentication uses OAuth 2.0 tokens for the REST API. Tokens can be user-scoped or product-scoped for fleet management. Device credentials are separate from cloud API credentials — the cloud API authenticates with user/product tokens while devices authenticate with device keys. Teams should use product-scoped tokens for automation agents managing specific fleets.

Documentation is comprehensive and covers the device API, event system, and OTA workflow clearly. The function call and variable read documentation are particularly useful for agents implementing remote device control. Teams evaluating Particle versus self-hosted IoT platforms (Balena, EdgeX) should compare the device networking requirements, pricing at fleet scale, and the managed versus self-hosted trade-off.