Integrations — Reliatic Documentation

Integrations

Reliatic connects to your existing CMMS, EAM, and operational data systems. Native connectors for SAP PM, IBM Maximo, Oracle EAM, and Infor EAM handle bi-directional sync without custom middleware. The REST API and webhook stream cover custom integration requirements.

CMMS / EAM Integrations

Native connectors use each CMMS's official API. Authentication credentials are stored in Reliatic's encrypted secrets vault—never in environment variables or configuration files. Configure under Settings → Integrations → CMMS.

SAP PM

NativeBi-directional

Synchronises notifications, orders, and functional locations between SAP Plant Maintenance and Reliatic. Work orders created in Reliatic are pushed to SAP as PM Notifications; completion status flows back automatically.

Field mappings

Equipment master → Asset register
Functional location → Asset hierarchy
PM Order → Work order / mitigation action
Notification → Governance event

IBM Maximo

NativeBi-directional

Integration via Maximo Application Framework REST API. Asset records, work orders, and PM schedules sync on configurable intervals. Maximo's site/org structure maps to Reliatic's facility/tenant hierarchy.

Field mappings

Asset → Asset register
Workorder → Work order
PMs → PM schedule tasks
Failure codes → FMEA failure mode taxonomy

Oracle EAM

NativeBi-directional

Connects to Oracle E-Business Suite EAM or Oracle Fusion Maintenance via REST/SOAP. Asset instances, maintenance activities, and meter readings synchronised.

Field mappings

Asset Instance → Asset register
Maintenance Work Order → Work order
Meter readings → Reliability metrics input

Infor EAM

NativeInbound (Infor → Reliatic)

Asset and work order data imported from Infor EAM via REST API. Supports Infor CloudSuite and on-premises deployments.

Field mappings

Equipment → Asset register
Work orders → Work order log
Failure codes → Failure event taxonomy

API Authentication

All API requests must be authenticated. Two methods are supported depending on integration type.

API Key

Authorization: Bearer <key>

Use for: Server-to-server integrations, CMMS connectors, scripts

Keys are tenant-scoped and carry the permissions of the service account they are bound to. Rotate under Settings → API → Keys.

OAuth 2.0 (Client Credentials)

POST /api/oauth/token

Use for: Enterprise SSO, external automation platforms

Token expiry configurable (default 1 hour). Refresh tokens supported. Required for multi-tenant enterprise deployments.

Webhook payload signing: All webhook payloads include a X-Reliatic-Signature header (HMAC-SHA256). Always verify this signature before processing webhook payloads. The signing secret is available under Settings → Integrations → Webhooks.

Webhook Events

Subscribe to platform events to trigger downstream workflows in your integration systems. Configure endpoint URLs and event subscriptions under Settings → Integrations → Webhooks. Multiple endpoints are supported; each can subscribe to different event sets.

Webhook payload envelope

{
  "event":      "governance.event.created",
  "tenant_id":  "t_a7f3c2",
  "timestamp":  "2026-02-18T09:14:22Z",
  "payload": {
    "asset_id":   "V-2041",
    "trigger":    "RPN_THRESHOLD_EXCEEDED",
    "risk_score": 312,
    "threshold":  200
  },
  "signature":  "sha256=..."
}

governance.event.created

A new governance event was fired for an asset

governance.event.resolved

A governance event was resolved with a governed artifact

governance.event.escalated

An event was escalated to the next authority tier

inspection.completed

An inspection record was submitted and signed off

inspection.overdue

An inspection passed its due date without completion

risk.score.changed

An asset's risk score changed by more than the configured delta

mitigation.overdue

A mitigation action passed its deadline

deviation.created

A formal compliance deviation was recorded

deviation.expired

A compliance deviation reached its expiry date

risk_acceptance.expiring

A risk acceptance will expire within the configured warning window

Rate Limits

Limits are applied per-tenant. Rate limit headers are included in all API responses: X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset.

Tier

Standard API

Steady-state limit

1,000 req/min per tenant

Burst

5,000 req/min (30-second window)

Tier

Bulk Import

Steady-state limit

10 MB payload per request

Burst

Async processing via job queue; no concurrency limit

Tier

Webhook delivery

Steady-state limit

100 events/sec delivery rate

Burst

Queue depth: unlimited; guaranteed delivery with retry

Tier

CSV/Excel Import

Steady-state limit

50,000 rows per file

Burst

Processed asynchronously; status at Settings → Imports

Getting Started

Generate an API key

Settings → API → Keys → New Key. Assign the minimum required permissions scope.

Select your CMMS connector

Settings → Integrations → CMMS. Enter your CMMS API endpoint and credentials.

Configure field mappings

Map your CMMS asset classification codes and failure codes to the Reliatic taxonomy.

Run an initial import

Settings → Imports → New Import. Select asset scope and review the mapping preview before committing.

Set sync schedule

Configure bi-directional sync interval (minimum 5 minutes). Recommended: 15-minute intervals for production.

Configure webhook endpoints

Settings → Integrations → Webhooks. Add endpoint URL, select event subscriptions, store signing secret.

← Analytics & Reporting API Reference →