Interactive flow

Build an integration step by step, with live calls

Each step sends a real request to the sandbox and shows the response. The diagram marks where the data comes from. Run them in order, or jump to the one you need.

SensorsVibration, CT, kWh meter
GatewayLoRaWAN
OPTIMUS ARSCondition, alarms, work
Open APIREST, webhooks, embed
Your systemBack end and front end

    Integration patterns

    Three ways teams use the API

    Most integrations combine them: webhooks for speed, a periodic sync as the safety net, and an embed where people need to see the machine.

    Pull · ERP or CMMS sync

    Keep work orders in step

    1. Every 5 to 15 minutes call GET /work-orders?updated_since=<last run>.
    2. Follow next_cursor until it is null.
    3. Upsert by id; store as_of as the next starting point.
    Push · alerting

    React within seconds

    1. Subscribe to alarm.raised and work_order.created.
    2. Check X-ARS-Signature, answer 2xx quickly, process later.
    3. Ignore an event_id you have already handled.
    Embed · portal

    Show the machine in your page

    1. Your back end calls POST /embed-tokens with the asset.
    2. Your page loads the returned embed_url in an iframe.
    3. Answer ars:token-expiring with a fresh token.