Overview
The ioX-Pulse public API lets your own applications read device data out of ioX-Pulse and act on your fleet: dashboards in a BI tool, a customer-facing portal, a mobile app, a scheduled export, or a system that sends downlinks to devices. It is a versioned REST API under /api/v1, served from the same domain you use to sign in.
Authentication
Every request to the API carries an API key as a bearer token. Keys are created and managed in the app, scoped to exactly what an integration needs, and shown in full only once.
Endpoints
This page lists the available endpoints with copy-paste examples. The full interactive reference, including every parameter, is built in at /api/v1/docs on your portal domain.
Webhooks
Webhooks are the push side of the API. Instead of your application asking ioX-Pulse for data on a timer, ioX-Pulse sends each event to a URL you choose, as it happens. This is the recommended way to react to new readings, alarms, and devices going on or offline in real time.
Rate limits and quotas
API usage is bounded by your plan. Two limits apply, both set by the tier on your partner account (and, for a sub-account key, the sub-account's tier as well, whichever is lower):