Overview
UniAsset supports multiple integration methods to connect with your existing business systems. This article summarises what is available today.
Available Integration Methods
| Method | Status | Minimum Plan |
|---|---|---|
| Integration REST API | Available | Business |
| Outbound webhooks | Available | Business |
| IoT signal ingestion | Available | Enterprise |
| CSV import / export | Available | All plans |
| Microsoft Entra ID (SSO + directory sync) | Available | Enterprise |
Integration API
The Integration API allows external systems to write asset data directly into UniAsset.
Supported operations:
| Operation | Endpoint | Permission |
|---|---|---|
| Create an asset | POST /api/integrations/assets/create | asset:create |
| Record maintenance | POST /api/integrations/assets/maintenance | maintenance:create |
| Assign an asset | POST /api/integrations/assets/assignment | assignment:update |
| Update geo-position | POST /api/integrations/assets/geo-position | asset:location |
| Ingest IoT signal | POST /api/integrations/iot/signals | iot:signal:ingest |
Authentication: Bearer API key (Authorization: Bearer ua_live_<key>)
Key management: Settings → Integrations → API Keys (Owner role required)
Full documentation: API Access
Webhooks
UniAsset sends signed HTTP POST requests to your endpoint when asset events occur.
Available events:
| Event | Trigger |
|---|---|
asset.created | A new asset is created |
asset.updated | An asset record is updated |
asset.assigned | An asset assignment changes |
geo_position.updated | Asset geo-position is updated |
maintenance.created | A maintenance record is created |
maintenance.due_soon | Maintenance is approaching its due date |
maintenance.overdue | Maintenance has passed its due date |
document.expiring | A linked document is near expiration |
document.expired | A linked document has expired |
document_asset.expiring | A document-type asset is near expiration |
document_asset.expired | A document-type asset has expired |
warranty.expiring | An asset warranty is near expiration |
incident.created | A new incident is recorded |
Security: Each webhook is signed with HMAC-SHA256. Verify the X-UniAsset-Signature header before processing. See Webhook Security Verification.
Configuration: Settings → Integrations → Webhooks
Minimum plan: Business
IoT Signal Ingestion
UniAsset's IoT Signal foundation (Phase 1) accepts telemetry from any IoT pipeline via a single HTTP endpoint and stores signals against the asset they belong to.
Supported sources: Azure IoT Hub, AWS IoT Core, custom MQTT bridges, any system capable of HTTPS POST.
Signals appear:
- On the asset detail page (most recent 10 signals with payload view)
- In the global IoT signal explorer at
/dashboard/iot-signals
Minimum plan: Enterprise
Setup guide: Connecting Azure IoT Hub to UniAsset
CSV Import / Export
All plans can import and export asset data in CSV format from the dashboard.
- Import: Dashboard → Assets → Import
- Export: Dashboard → Assets → Export or Reports
Microsoft Entra ID (SSO + Directory Sync)
Enterprise customers can integrate with Microsoft Entra ID (formerly Azure Active Directory) for:
- Single Sign-On (SSO): Team members sign in via their Entra credentials
- Directory sync: Users are provisioned and deprovisioned automatically as they join or leave your Entra directory
Minimum plan: Enterprise
Configuration: Settings → Integrations (Entra tab)
CSV vs API: Which to Use
| Scenario | Recommended method |
|---|---|
| One-time bulk import of existing assets | CSV import |
| Ongoing sync from an ERP or procurement system | Integration API |
| Receiving IoT telemetry from devices | IoT signal ingestion endpoint |
| Triggering downstream workflows when assets change | Webhooks |
| Managing user identity and access | Entra ID SSO |
Related Articles
Need Help?
If you have questions not covered in this article, our support team is here to help.
Contact Support