canonical: https://jentic.com/apis/maintenanceconnection.com/maintenanceconnection # Maintenance Connection API Jentic publishes the only available OpenAPI specification for Maintenance Connection API, keeping it validated and agent-ready. Maintenance Connection is a Computerized Maintenance Management System (CMMS) and its v8 REST API exposes 136 endpoints covering assets, work orders, parts and inventory, purchase orders, classifications, companies, and document management. The API uses HTTP basic auth and is the integration surface for plant-floor automation, asset tracking, and preventive maintenance workflows. ## For AI agents Manage CMMS assets, work orders, inventory, and purchase orders in Maintenance Connection. Used by agents that automate preventive maintenance scheduling, parts ordering, and asset record-keeping for facilities and plants. ## Scope Does not handle accounting, payroll, or general-purpose CRM - use for CMMS asset, work-order, parts, and purchase-order operations only. ## Capabilities - Open a new work order against a specific asset and assign a technician - Record meter readings on an asset to drive condition-based maintenance triggers - Look up the parts inventory level for a stock item across multiple warehouses - Attach photos and documents to an asset record for compliance reviews - Create a purchase order for replenishment parts and route it for approval - Pull every work order completed against an asset for a reliability report ## Use cases ### Preventive Maintenance Automation Plant maintenance teams run preventive maintenance schedules driven by meter readings and elapsed time. The Maintenance Connection asset and meter-history endpoints record the readings that trigger PM work orders, and the work-order endpoints open, assign, and close the resulting jobs. An automation script can poll telemetry, post readings, and watch the system generate the right PMs without manual entry. Example prompt: POST `/Assets/{assetPK}/meterhistory` with the new reading and verify the resulting PM work order on GET /WorkOrders. ### Spare Parts Inventory Replenishment Stockouts on critical spare parts cause unplanned downtime. The Maintenance Connection inventory endpoints expose stock levels by warehouse and the purchase-order endpoints create and route POs for replenishment. A nightly batch can identify items below reorder point, generate the purchase orders, and capture the PO numbers for tracking. Example prompt: Query parts below reorder point, POST /PurchaseOrders with the consolidated reorder list, and capture the returned PO numbers. ### Asset Document and Photo Management Compliance reviews and reliability investigations need quick access to asset documentation, including manuals, inspection reports, and condition photos. The asset documents and images endpoints upload binary files against the asset record and list everything attached to a given asset, making it possible to compile a full asset dossier programmatically. Example prompt: POST `/Assets/{assetPK}/documents` with the inspection PDF, then list all documents on the asset to confirm the upload. ### AI Agent Maintenance Assistant Maintenance supervisors can delegate routine work order creation, status checks, and parts lookups to an AI agent. Through Jentic the agent searches by intent, loads the schema for the right CMMS operation, and executes the call while basic-auth credentials stay in the vault. The same loop powers shop-floor copilots and supervisor chatbots. Example prompt: Use Jentic to search 'create maintenance work order', execute POST /WorkOrders with the asset and description from the user request, and return the new work order ID. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/Assets` | List all assets | | POST | `/Assets` | Create one or more assets | | GET | `/Assets/{assetPK}` | Get asset by PK | | POST | `/Assets/{assetPK}/meterhistory` | Create asset meter history records | | POST | `/Assets/{assetPK}/images` | Upload asset images | | POST | `/Assets/{assetPK}/documents` | Upload asset documents | | GET | `/AssetSpecifications` | List all asset specifications | ## Key resources - **Assets** — Create, list, fetch, and update assets including specifications, meter history, images, and documents. - **Work Orders** — Open, assign, update, and close work orders against assets and locations. - **Inventory and Parts** — Track parts, stock levels, and warehouses across the maintenance organisation. - **Purchase Orders** — Create and manage purchase orders for replenishment and outside services. - **Classifications** — Manage classification hierarchies that categorise assets, parts, and work orders. - **Companies** — Manage vendor, contractor, and customer company records linked to assets and POs. ## Why Jentic - **Setup:** Wiring the Maintenance Connection API by hand means encoding its ConnectionKey and APIKey as HTTP basic auth, targeting the api.maintenanceconnection.com/v8 host, and mapping across its many CMMS asset and work-order endpoints yourself. Through Jentic you install once, import Maintenance Connection from the API Directory, store the credentials once, and your agent calls it. - **Permission scoping:** Maintenance Connection puts the asset id in the URL path (`/Assets/{assetPK}`, `/Assets/{assetPK}/meterhistory`), so a rule can pin your agent to one asset. You choose the operations it may call, so creating an asset or attaching documents is not included unless you add it. - **Credential handling:** Your Maintenance Connection ConnectionKey and APIKey are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'look up an asset' or 'record meter history', and Jentic returns the matching Maintenance Connection operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **UpKeep API** — UpKeep is a competing mobile-first CMMS with overlapping work order and asset endpoints. - **HubSpot Account Info API** — HubSpot manages customer relationships that often link to assets and service contracts in a CMMS. ## FAQ ### Why is there no official OpenAPI spec for Maintenance Connection API? Maintenance Connection does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Maintenance Connection API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Maintenance Connection API use? Maintenance Connection uses HTTP basic authentication: the username and password of a Maintenance Connection account user. Through Jentic the credentials are stored encrypted in the vault and injected at execute time, so they never enter the agent context. ### Can I open a work order against an asset through the API? Yes. The work-order endpoints accept the asset PK, description, and assigned technician on POST and return the new work-order PK. Use GET on the same resource to track status updates. ### How do I record a meter reading on an asset? Call POST `/Assets/{assetPK}/meterhistory` with the meter reading payload. The reading drives any meter-based preventive maintenance schedules attached to the asset. ### What are the rate limits for the Maintenance Connection API? The OpenAPI spec does not declare numeric rate limits - they are governed by the Maintenance Connection deployment your account belongs to. Confirm the limit with your Maintenance Connection administrator before driving high-volume integrations. ### How do I open a work order through Jentic? Run pip install jentic, search 'open a maintenance work order', load the schema for the work-order POST, and execute with the asset PK and description. Jentic injects the basic-auth header from the encrypted vault. ### Can I limit what my agent is allowed to do with the Maintenance Connection API? Yes. Because you run Jentic One yourself, your own rules decide which Maintenance Connection operations and credentials the agent may use. Since the asset PK sits in the URL path on endpoints like `/Assets/{assetPK}` and `/Assets/{assetPK}/meterhistory`, you can pin the agent to a single asset, and you pick which operations it may call, so opening a work order or reading meter history is allowed while creating assets or uploading documents stays off unless you add it. The basic-auth credentials are held by your own instance and injected only at execution time, never reaching the agent's context.