Slack and Teams are live, native, and documented to the field level. For everything else — ERP, identity, IoT — our REST API gives you the same access our own mobile app uses. Build it in an afternoon, or tell us what to build next.
Most CMMS vendors list 50+ “integrations” that are CSV imports with a logo on them. We ship two: Slack and Teams. Both native, both documented to the field level, both with actions — not just read-only alerts.
High-priority work orders post to the channel you choose with a one-click Acknowledge button. P1 issues page on-call automatically. Nobody has to remember to open the CMMS at 2am.
Work order alerts arrive as Adaptive Cards in the channel you choose. Technicians acknowledge, comment, or close directly from Teams — no separate app to open, no login to remember.
Our API isn't an afterthought. It's how our own mobile app talks to the backend — so everything the product does, the API does too. Public-facing since v1, never had a breaking change.
# Create a work order from a sensor alarm curl https://api.assetos.com/v1/work-orders \ -H "Authorization: Bearer $AOS_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "asset_id": "ast_8f2k3", "title": "Pump 4B vibration > threshold", "priority": "p1", "source": "sensor.vibration", "metadata": { "reading": 4.2, "threshold": 3.5 } }' # → 201 Created # → Webhook fired: work_order.created
Subscribe once, route where you like. Every event is signed, retryable, and replayable from the dashboard for 30 days.
Every quarter we look at the most-requested connectors and build the top three ourselves, at no charge to customers. The last three were Greenhouse, Maximo, and Oracle NetSuite.
We use cookies to analyze site traffic and improve your experience. Learn more