Reference · built on requestConnectorField service & CMMS

MaintainX

Work orders, work requests, assets, parts, meters, and procedures from MaintainX REST API v1, with webhook subscriptions.

Request accessPricing ↗

About

MaintainX is a CMMS for maintenance and operations teams. Its API v1 at https://api.getmaintainx.com/v1 covers work orders, work requests, assets, locations, parts, purchase orders, meters, meter triggers, maintenance plans, procedure templates, work permits, custom fields, teams, users, and vendors. Lists page by cursor. Subscriptions post events such as NEW_WORK_ORDER and ASSET_STATUS_CHANGE to a URL, signed with a per-subscription HMAC secret.

An operator on Fibric listens for work order and asset events, reads the records behind them, and proposes a new work order, a status change, or a part reorder for your approval, with a receipt for each.

This is a reference listing. It documents what Fibric would read from MaintainX and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Work orders from /workorders with comments, costs, part status, sub-work-orders, and procedure fields
  • Work requests from /workrequests and the portals that collect them
  • Assets with ONLINE and OFFLINE status history, criticalities, custom statuses, manufacturers, and models
  • Meters, meter readings, and meter triggers with their work order templates
  • Parts, part transfer requests, purchase orders with fulfilment state, and vendor contacts
  • Events by subscription: NEW_WORK_ORDER, WORK_ORDER_STATUS_CHANGE, WORK_ORDER_OVERDUE, NEW_WORK_REQUEST, ASSET_STATUS_CHANGE, METER_TRIGGER_STATE_CHANGE, PART_QUANTITY_CHANGE

Proposed actions

  • Target capability: propose a work order through POST /workorders, or a status change through PATCH /workorders/{id}/status
  • Target capability: propose a comment or cost on a work order
  • Target capability: propose an asset status change through POST /assets/{assetId}/status
  • Target capability: propose meter readings, batched through POST /meterreadings
  • Target capability: propose a purchase order or a status or fulfilment update on one

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Stop a line and open the job in one motion

    On ASSET_STATUS_CHANGE to OFFLINE, read the asset and open work, then propose a work order with the right procedure template and team.

    With Line Downtime, Predictive Maintenance

  • Chase the overdue before the shift ends

    Subscribe to WORK_ORDER_OVERDUE, read assignees and priority, and propose a reassignment or priority bump for the supervisor.

    With Backlog Priority, Work Order Aging

  • Reorder when a part count drops

    On PART_QUANTITY_CHANGE, compare quantity to the part's minimum and propose a purchase order to the linked vendor.

    With Parts Reorder

  • Check the permit before hot work starts

    Read the work order, its procedure fields, and the permit sign state; propose holding the job until the permit is signed.

    With Permit Check, Hot Work Permit

Requirements

  • A MaintainX organization on the Premium or Enterprise plan, where API access is available
  • An API key created for the user the connector acts as
  • A public HTTPS URL to receive subscription events, and the secret from /subscriptions/{id}/secret to check signatures
  • The Enterprise plan for Automated meters that store high-frequency readings from integrations
Authentication
A bearer token generated for a user under Settings > Integrations > API Keys, sent as Authorization: bearer {token}.

Limits

  • Manual meter readings are limited to 10 requests per 24 hours; Automated and IoT readings to 100 requests per 60 seconds
  • A batched readings request counts as one request toward that limit
  • Lists page forward only, by cursor and limit, using nextCursor and nextPageUrl
  • The v1 reference exposes work permits only for signing, through /workPermits/{id}/sign

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request MaintainX ↗

Questions and answers

Which plans include the API?
Premium and Enterprise. The reference states API access is available on those plans, and keys are generated per user under Settings > Integrations > API Keys.
How are webhook payloads secured?
Each subscription has a secret, fetched from GET /subscriptions/{id}/secret, used to hash an HMAC signature on deliveries. Subscriptions are created with POST /subscriptions naming an event type and a URL; some types accept filters, such as asset status types.
How do lists page, and can records be addressed by my own IDs?
List endpoints take cursor and limit. Responses carry nextCursor and nextPageUrl for the following page. Records can also be addressed by your own identifier through /workorders/external/{externalId} and matching routes for assets, locations, and parts.
Ask about MaintainX

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with MaintainX through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy