REST API & SDK
APIs, webhooks, and scheduled exports keep machine data available outside the platform.
The REST API and SDK expose devices, variables, events, and history. CSV and PDF cover operational reporting, while webhooks push state changes into external systems. These routes provide a practical exit path as well as an integration surface.
The data path, including the hand-offs that usually cause trouble.
Authenticate
Issue scoped API tokens by tenant and application. A read-only analytics key cannot call a control endpoint.
Query
Documented REST endpoints expose devices, variables, events, and paginated time-series history with filtering.
Subscribe
Webhooks push state changes to downstream systems instead of requiring a polling loop.
Export
CSV and PDF exports, on demand or on a schedule, delivered to the people who need them.
Where teams use this integration.
Keep the warehouse as the source of truth
Telemetry history can move through REST into the warehouse and governance model the organisation already uses.
Month-end numbers without chasing operations
Scheduled consumption and runtime exports can arrive on the first day of the month, ready for reconciliation.
A concrete answer to vendor risk
Full exports and an available 10-year perpetual licence give the board specific options if platform ownership changes.
Want this wired into your stack?
Bring the source system, target system, and security constraints. An engineer will map the interface and the unresolved questions.