Your Data, in Your Own Systems
ioX-Pulse has a versioned REST API under /api/v1, served from the same domain you sign in to, with a browsable interactive reference and an OpenAPI description you can generate a client from. Read devices, latest values and history, send downlinks, manage sites, networks and sub-accounts.
For anything that needs to be current rather than requested, webhooks push each event to a URL you choose as it happens: a decoded reading, a device going quiet, an alarm opening or clearing. Every delivery is signed, retried on a published schedule, and recorded in a log you can read.
- A versioned REST API with an interactive reference and an OpenAPI description
- Keys scoped to exactly what an integration needs, shown once and stored hashed
- Signed webhook deliveries you can verify, with the algorithm published rather than described
- A retry schedule you can plan around, and a delivery log you can read
- Endpoints that cover the operational surface, not just a read-only export
- Rate limits published with the headers a well-behaved client needs to stay under them
Trusted by teams monitoring critical infrastructure
What happens when it fails
Signatures, Retries and Dead Endpoints
Deliveries are sent by a background worker, so they arrive within about a minute rather than in the same instant, and your endpoint should answer quickly and do the slow work afterward.
| Behavior | What it means for you |
|---|---|
| Every delivery is signed | Each webhook has its own signing secret, and each request carries a timestamp and an HMAC-SHA256 signature over that timestamp and the raw body. Verify it before trusting the payload. The algorithm is published, not merely asserted. |
| Failures are retried on a schedule | A failed delivery is retried immediately, then after thirty seconds, then five minutes, then thirty. After the last attempt it is marked failed rather than retried forever. immediate 30s 5m 30m |
| A dead endpoint gets switched off | After repeated consecutive failures the webhook is disabled automatically, so a broken receiver stops generating traffic. Re-enable it once your endpoint is healthy and the failure count resets. |
| Retries can duplicate | Each delivery carries a unique id so you can recognize one you have already handled. Make your receiver idempotent; anything that retries will eventually deliver twice. |
| There is a delivery log | You can see what was sent and what came back, rather than guessing from your own side of the connection. |
Two things the platform will not do: deliver to a plain HTTP URL, and deliver to an address that resolves somewhere internal, such as a private range, loopback or a cloud metadata endpoint. Both are checked when you save the webhook and again at delivery time.
