Create a work order and attach assets/tasks to it using Fiix CMMS's object-based CRUD API.
domain: fiixlabs.github.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Generate an Application Key, Access Key, and Secret Key under Settings > Connect Management > API Application Settings as an administrator (works against a free sandbox for Enterprise-plan accounts).
Use the add method with className WorkOrder and required fields (e.g., intSiteID, intWorkOrderStatusID) to create the work order.
Associate assets via className WorkOrderAsset (intWorkOrderID + intAssetID) and add checklist tasks via className WorkOrderTask.
Use find/findById with an explicit fields list and dv_-prefixed fields to get human-readable display values for related records instead of raw IDs.
Batch multiple add/find calls into one batch request when creating a work order with several associated assets/tasks, since batch requests are transactional (all-or-nothing).
Known gotchas
The API account's permission level (whichever Fiix user group the keys are tied to) governs everything the integration can see/do — assign it to a scoped user, not an admin, in production.
Fields use a Hungarian-notation naming scheme (intWorkOrderID, strName) that must match exactly — there's no camelCase alias.
The Java/JavaScript SDKs are the documented path; using raw HTTP without an SDK is possible but far less documented in a separate 'no-SDK' guide.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?