Slack · Teams · Geotab (in build) · REST API · Webhooks

AssetOS plays nicely with the
stack you already have.

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.

Slack + Teams

Native integrations, live today

REST API

Full CRUD — same endpoints our app uses

Webhooks

Outbound events on every write

Zero

Middleware required — connect direct

Two shipped. One in build.

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. Geotab is the third, in build now, and the page says plainly what it will and won't do.

AOSl

Native

Slack

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.

Sync directionPush + actions

FrequencyReal-time

AuthSlack OAuth

ActionsAck, comment, close

AOTe

Native

Microsoft Teams

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.

Sync directionPush + actions

FrequencyReal-time

AuthTeams OAuth

ActionsAck, comment, close

AOGt

In build

Geotab

Odometer and engine hours from Geotab trigger preventive maintenance on how hard a vehicle actually worked. Fault codes raise work orders the same day they fire. In build — first fleets live September 2026.

Sync directionGeotab → AssetOS

ReadsMeters, DTCs, position

AuthMyGeotab API

StatusEarly access list

What it will and won't do →

REST API · OpenAPI 3.1

Not on this list?
Build it in an afternoon.

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.

OpenAPI 3.1 spec with generated clients for 8 languages
Webhooks for all key event types, signed with HMAC-SHA256
Rate limits published, 5k req/min on Standard, no soft caps
Sandboxes with 1-click reset, included on every plan
No enterprise-only endpoints — what you see is what you get

Read the docs →Get API key

# Create a work order from a sensor alarm
curl https://api.assetos.io/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

Webhook events. All documented.

Subscribe once, route where you like. Every event is signed, retryable, and replayable from the dashboard for 30 days.

work_order.created

work_order.assigned

work_order.status_changed

work_order.closed

asset.created

asset.location_changed

asset.status_changed

part.stock_low

part.consumed

pm.schedule.due

pm.schedule.overdue

sensor.reading.alarm

ai.anomaly.detected

invoice.matched

user.invited

See all events in the docs →

Missing an integration?
Tell us — we build the
most-requested ones free.

Tell us what you need to connect to and we'll build it — native connectors go on the roadmap free, and we'll show you how to wire it up with the REST API in the meantime.

AssetOS plays nicely with thestack you already have.