API access
Let your other systems use the same maintenance record.
MaintenanceIQ API access is a token-authenticated API so your other systems can read and write the maintenance records your team already keeps in the app. It covers work orders, assets, breakdowns and machine readings, inside your organization only. It helps your IT team connect a PLC, an ERP or a dashboard without a second copy of the plant's history.
What it is for
One record, reached by a token
Plants already have systems that know a machine stopped, a counter moved, or a part was booked. MaintenanceIQ's API is how those systems talk to the same record the planner and the technician use. A token identifies the integration and keeps it inside your organization. The token cannot see another customer's data.
The API is the wider door around a path that already existed. A PLC, SCADA system or IoT gateway can push parameter readings, and a reading that crosses a critical limit can still open a breakdown. The same access now lets an authorized system create a work order or a breakdown when it already knows a machine has stopped, and read assets, work and downtime back out.
CSV and Excel import, and CSV export from the report builder, stay in place for a team that does not want to write an integration. The API is for the connection that should run without someone uploading a file.
What an integration can do
| Job | What moves | What the plant sees |
|---|---|---|
| Send machine readings | Values from a PLC, SCADA system or IoT gateway, against the parameters you already set | The same warning and critical limits, and a breakdown when a reading is critical |
| Open work from another system | A work order or a breakdown for a machine that system already knows | A job on the planner's list, tied to the asset, ready for a technician |
| Read the record back | Assets, open and closed work, and downtime | The same numbers the plant head sees, in the system that asked |
The token acts inside your organization. It does not bypass role checks, and it does not reach another tenant.
A first connection
Start with one flow, on one line
Pick the flow that already hurts. If readings sit in a historian and nobody acts on them, send those readings first and confirm a critical value opens a breakdown on the right asset. If another system already raises a job in a spreadsheet, have it create the work order instead, on one line, for a week.
Issue a token for that integration and for that organization. Keep the token with the system that uses it, the way you would keep any other credential. When the project ends or the vendor changes, revoke the token. Past records stay. The integration simply stops.
Read something back before you call the connection done. An asset, a closed work order and a downtime total should match what a planner sees in the app. If they do, the other system is using the maintenance record. If they do not, fix the mapping before you add a second flow.
We do not ship ready-made connectors to named ERP or MES products. Your team, or ours during implementation, uses the API. Your system calls MaintenanceIQ. MaintenanceIQ does not call your server when a record changes, so if you need a live push into another product, plan a scheduled read.
- One token, one organization, one flow to start
- Readings in, or a work order created from a known stop
- A read-back that matches the screen a planner already trusts
- Revoke the token when the integration should stop
What stays true when a system is connected
Tenant isolation
The token belongs to your organization. Another customer's assets, work orders and readings are not in reach.
The same permissions
An integration does not skip the access checks the app uses. It works within the access you gave that token.
The audit log
Writes still record who changed what, and when. A job opened through the API is a job on the log, not a side door.
Files stay private
Photos, certificates and evidence packs stay in private storage and open through short-lived signed links, the same as in the app.
The records the API sits on
- Condition monitoringLimits, alerts and the readings path from a PLC, SCADA or IoT gateway.
- Work ordersThe job an integration can open, and a technician can close.
- Single sign-onThe company login for the people, beside the token for the systems.
- SecurityIsolation, the audit log, and the controls around both.
Frequently asked questions
Does MaintenanceIQ have an API?
Yes. A token-authenticated API lets other systems read and write maintenance records inside your organization: work orders, assets, breakdowns and machine readings.
Can a PLC or SCADA system send readings?
Yes. A PLC, SCADA system or IoT gateway can push readings through the API. Each reading is checked against the warning and critical limits you set, and a critical reading can open a breakdown.
Are there ready-made connectors to named ERP or MES products?
No. You connect those systems through the API, or you keep using CSV and Excel import and CSV export. We do not ship a connector branded for a named ERP or MES.
Will MaintenanceIQ call our server when a record changes?
No. Your system calls MaintenanceIQ. If you need the data in another product, have that product read it on a schedule.