Particle
Connect Particle to the rest of your business, with the right person approving what changes and a record of every action.
25 ways to read, 1 way to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Particle, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Rename device or edit notes
device.updateApproval by rule - List authorised devices
devices.listRead
Example flow
- Particle · List authorised devices
devices.listDone - Particle · Rename device or edit notes
device.updateMaker-checker - Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Particle.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Particle
- Particle's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Particle IoT devices, products, fleet groups, vitals, SIMs, firmware, integrations, ledgers, locations and Logic runs, read-only apart from device names and notes.
Particle API docs- Source actions
- 25
- Destination actions
- 1
- Data types
- 23
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
device variable1
- Read device variableSource
Read the current value of a variable exposed by the device firmware.
device2
- Get deviceSource
Read one device's status, firmware, groups and exposed function and variable names.
- Rename device or edit notesDestinationProvider duplicate protectionApproval before production
Change a device's name and/or notes. No other device attribute can be changed.
devices1
- List authorised devicesSource
Devices visible to the authenticated Particle user.
diagnostics2
- Get last device vitalsSource
Read the last device vitals payload sent to the Device Cloud.
- List device vitals historySourceIncremental
Read stored device vitals records (kept for one month).
firmware2
- Get product firmware versionSource
Read one product firmware version.
- List product firmwareSource
List uploaded product firmware versions and their release state.
group1
- Get device groupSource
Read one device group with its device count.
groups1
- List device groupsSource
List a product's device groups.
integration1
- Get integrationSource
Read one integration's metadata.
integrations1
- List integrationsSource
List webhook and cloud integrations (metadata only).
ledger instance1
- Get ledger instanceSource
Read one ledger instance by scope value (for example a device ID).
ledger instances1
- List ledger instancesSource
List a ledger's instances with their data.
ledger1
- Get ledger definitionSource
Read one ledger definition.
ledgers1
- List ledger definitionsSource
List ledger definitions in the sandbox or a product.
location1
- Get device locationSource
Read last known or historical location for one product device.
locations1
- List device locationsSource
Read last known or historical locations for a product's devices.
logic functions1
- List Logic functionsSource
List Particle Logic functions with triggers and today's run statistics.
logic runs1
- List Logic function runsSource
List recent runs of a Logic function.
product devices1
- List product devicesSource
List a product fleet's devices with optional filters.
product1
- Get productSource
Read one product's settings summary.
products1
- List productsSource
List products the token can access.
sim data usage1
- Get SIM data usageSource
Read the current billing period's data usage by day.
sim1
- Get SIM cardSource
Read one SIM card's status and carrier.
sims1
- List SIM cardsSource
List SIM cards owned by the user or a product.
Access and limits
- Authentication
- Particle access token (Bearer); an API user token scoped to the needed reads is recommended
- Plans and access
- Particle account; product, organization, ledger and Logic endpoints need the matching plan and team access. Use a product or organization API user limited to the read scopes in use plus devices:update only if name or notes edits are enabled.
- Test environment
- Particle Sandbox (free tier) accounts can be used for testing.
- Rate limits
- Particle allows 10,000 API requests per 5 minutes per source IP, with lower limits for token, user and event endpoints. HTTP 429 uses bounded retries and Retry-After.
- Pagination
- Sandbox device listing is an unpaginated array. Product devices, SIMs, ledgers, ledger instances and locations use page and perPage with meta.total_pages.
- Provider events
- Particle integrations (webhooks) forward device events to HTTPS endpoints. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Device events are only available from Particle as Server-Sent Event streams; the Nexra recipe engine handles request/response calls only, so event reads are not implemented. Use a Particle webhook integration to forward events.
- Excluded because they act on hardware or cannot be undone: calling functions, publishing events, flashing or releasing firmware, ping, signal, Service Mode, ledger writes, SIM activation, deactivation or release, claiming, unclaiming, quarantine approval and all deletes.
- Device updates only change the name or notes. Group membership, development mode and firmware locks are excluded because they can trigger over-the-air firmware updates.
- Reading a device variable queries the live device; offline devices return an error.
- Integration responses can contain target URLs, headers and credentials; only integration metadata is returned.
- Organization-scoped (/v1/orgs/...) variants and Logic run logs are not implemented.
Developer reference
- Create the Particle credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Particle, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/particle and the Connections API.