canonical: https://jentic.com/apis/fiix.io/fiix # Fiix CMMS API Fiix (by Rockwell Automation) is a cloud-based Computerized Maintenance Management System (CMMS) used by manufacturers to track assets, work orders, parts, and scheduled maintenance. The API exposes 25 endpoints, with both a single /rpc operation-based JSON pattern and direct REST paths for assets, work orders, parts, purchase orders, and users. Authentication supports apiKey via the Authorization header and OAuth2 for delegated app access. ## For AI agents Manage industrial assets, work orders, scheduled maintenance, parts inventory, and purchase orders in Fiix CMMS via 25 endpoints with API key or OAuth2 auth. ## Scope Does not handle ERP general ledgers, payroll, or production scheduling - use for CMMS assets, work orders, parts inventory, and preventive maintenance only. ## Capabilities - Create, update, and close work orders against specific assets - Track asset hierarchies including parent-child relationships and locations - Schedule recurring preventive maintenance tied to assets - Manage spare parts inventory with reorder points - Issue purchase orders for parts replenishment - Execute generic CMMS operations via the unified /rpc endpoint ## Use cases ### Reactive Maintenance Workflow Create work orders the moment a fault is detected by an upstream telemetry system. The Fiix API exposes POST /workorders linked to an asset_id so an agent can spawn the work order from sensor alerts without manual technician entry. Cuts mean-time-to-acknowledge from hours to seconds in industrial maintenance shops. Example prompt: POST /workorders with asset_id and a description from the alert payload, then GET `/workorders/{id}` to confirm creation ### Preventive Maintenance Scheduling Surface upcoming preventive maintenance tasks across a fleet of assets so planners can stage parts and labour ahead of time. The Fiix API exposes scheduled-maintenance endpoints joined with asset records, supporting weekly look-aheads typical in plants with hundreds of assets. Example prompt: List scheduled maintenance with due_date in the next 7 days, then resolve each asset_id to its location and group results by site ### Parts Inventory Replenishment Automate parts replenishment by joining current inventory with reorder thresholds and issuing purchase orders. The Fiix API exposes /parts and /purchaseorders endpoints, so an agent can detect low stock and create a PO in one workflow. Replaces manual stock-checks common in maintenance stockrooms. Example prompt: GET /parts, filter by quantity_on_hand below reorder_point, and POST /purchaseorders for the affected parts ### AI Agent Maintenance Assistant via Jentic Through Jentic, an agent can answer plant-floor questions like which assets are overdue for service and which open work orders are blocked on parts. Jentic exposes Fiix's work order, asset, and parts operations as discoverable tools so a Claude or GPT agent can run grounded maintenance queries from natural language. Example prompt: Search Jentic for 'list work orders', call GET /workorders, and return open ones grouped by asset and aged over 7 days ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/rpc` | Execute an RPC operation | | GET | `/assets` | List assets | | POST | `/assets` | Create an asset | | GET | `/workorders` | List work orders | | POST | `/workorders` | Create a work order | | GET | `/parts` | List parts inventory | ## Key resources - **Assets** — Industrial equipment with hierarchy and locations - **Work Orders** — Maintenance tasks tied to assets - **Parts** — Spare parts inventory with reorder thresholds - **Purchase Orders** — Replenishment orders for parts - **Scheduled Maintenance** — Recurring preventive maintenance schedules - **Sites** — Physical locations housing assets - **Users** — Technicians and planners with assigned roles - **Operations** — Generic CMMS operations via the /rpc endpoint ## Why Jentic - **Setup:** Wiring the Fiix CMMS API by hand means resolving your {tenant} subdomain, choosing between API-key and OAuth2 auth, and driving the /rpc endpoint alongside the REST assets and work-order routes yourself. Through Jentic you install once, import the Fiix CMMS API from the API Directory, store the key and tenant once, and your agent calls it. - **Permission scoping:** Fiix work-order and asset targets travel in the request body and its /rpc payload rather than as owned-resource path ids, so limit the agent to the operations it needs, such as listing assets or creating a work order, and leave the rest out. Because you choose the allowed operations, a write runs only if you include it. - **Credential handling:** Your Fiix API key or OAuth2 token and tenant value are stored once, encrypted, by your own Jentic One instance and injected at execution time. The raw Authorization header value never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create a work order' or 'list parts inventory', and Jentic returns the matching Fiix operation with its input schema, so the agent calls it without reading the API guide. ## Related APIs - **UpKeep API** — CMMS alternative oriented toward smaller facilities and mobile-first technicians - **Maintenance Connection API** — Enterprise CMMS alternative with on-prem deployment options - **Samsara API** — Industrial telemetry that triggers Fiix work orders from sensor alerts ## FAQ ### What authentication does the Fiix CMMS API use? Fiix supports two methods: an API key sent in the Authorization header and OAuth2 for delegated apps. Through Jentic both are encrypted in your Jentic One instance and never enter agent context. ### What is the /rpc endpoint in the Fiix API? POST /rpc accepts an operation-based JSON request that maps to internal Fiix actions. It complements the direct REST paths and is used for actions that do not have a dedicated path in the OpenAPI spec. ### What are the rate limits for the Fiix CMMS API? Fiix does not publish per-second limits in the OpenAPI spec; consult fiixlabs.github.io/api-documentation/guide.html for plan-specific quotas applied per tenant. ### How do I create a work order through Jentic? Search Jentic for 'create work order', load the POST /workorders schema, and execute with asset_id and description. Run pip install jentic to start. ### Does the Fiix API support multi-tenant deployments? Yes. The base URL https://{tenant}.machinemetrics.io/api/v2 contains a tenant variable so each customer addresses their own subdomain. Jentic stores the tenant value alongside the credential. ### Can I track parts inventory with the Fiix API? Yes. The Parts endpoints expose quantity_on_hand and reorder_point fields and the Purchase Orders endpoints let you replenish low-stock parts in a single workflow. ### Can I limit what my agent is allowed to do with the Fiix CMMS API? Yes. Because Jentic One is self-hosted, you decide which Fiix operations your agent can reach, so you can allow read-only calls like listing assets or work orders while withholding writes such as creating a work order or issuing a purchase order. Fiix passes its work-order and asset targets in the request body and the /rpc payload rather than as owned-resource path ids, so the operation allowlist you set is what governs access. A write runs only if you have included that operation, and the API key and tenant value stay under your control.