Fiix CMMS API

Name: Fiix CMMS API API
Brand: Fiix CMMS API
Availability: InStock

✓ Official Vendor SpecIOTDevice ManagementapiKey,oauth225 EndpointsREST

For 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.

Connect the Fiix CMMS API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Fiix CMMS API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Fiix CMMS API API.

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

GET STARTED

Start building with Fiix CMMS API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Fiix CMMS API API for, with concrete tasks.

★ 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.

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.

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.

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.

Search Jentic for 'list work orders', call GET /workorders, and return open ones grouped by asset and aged over 7 days

Key Endpoints

25 endpoints — 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.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Fiix API keys, OAuth2 tokens, and tenant subdomain values are stored encrypted in the Jentic MAXsystem vault. Agents receive scoped access — the raw Authorization header value never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'create a work order') and Jentic returns the matching Fiix POST /workorders operation with its schema, so the agent calls it without reading the API guide.

Time to first call

Direct Fiix integration: 3-5 days for tenant subdomain handling, OAuth, and /rpc operation mapping. Through Jentic: under 2 hours — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

UpKeep API

CMMS alternative oriented toward smaller facilities and mobile-first technicians

Choose UpKeep for SMB facilities; choose Fiix for industrial manufacturers needing deeper asset hierarchies.

Alternative

Maintenance Connection API

Enterprise CMMS alternative with on-prem deployment options

Pick Maintenance Connection when on-prem deployment is mandated; Fiix is cloud-only.

Complementary

Samsara API

Industrial telemetry that triggers Fiix work orders from sensor alerts

Pair Samsara with Fiix when telemetry-driven work order creation is needed.

FAQs

Specific to using Fiix CMMS API API through Jentic.

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 MAXsystem 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.