The API Report CardAPI Index
Fiix

Fiix API

fiixsoftware.com

Fiix has a genuinely documented API with public Java and JavaScript SDKs, but it is a proprietary JSON-over-HTTP RPC, explicitly not REST. Access requires the Enterprise plan, auth is a three-key static model with no OAuth, and calls are capped at 1,000 per day per user license.

Last verified: July 2026Manufacturing
API GRADE
D
VERIFIED JUL 2026

SCORECARD

ExistencePOORThe API is a Fiix-specific JSON-over-HTTP RPC convention, not REST or SOAP; generic OpenAPI tooling does not apply.
AccessPOOREnterprise plan only; Lite, Basic, and Professional tenants must upgrade, and there is no public sandbox or self-signup.
CoveragePOORv6 Work Orders and Equipment have no API path to v5 objects, so integrators juggle schema versions per tenant.
AuthPOORThree static keys (application, access, secret) provisioned per tenant; no OAuth 2.0, scopes, or token refresh.
Docs & DXGOODPublic developer guides plus first-party Java and JavaScript SDKs and sample code on GitHub.
StabilityMIXEDA hard cap of 1,000 calls per day per user license, and the v6 schema migration breaks v5 symmetry.
Supergood: Fiix has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Fiix scores D on the API Report Card. Fiix has a genuinely documented API with public Java and JavaScript SDKs, but it is a proprietary JSON-over-HTTP RPC, explicitly not REST. Access requires the Enterprise plan, auth is a three-key static model with no OAuth, and calls are capped at 1,000 per day per user license.

Tried to integrate with Fiix?
SOURCES
Hard 1,000 API calls per day per user license cap, for a 10-user tenant that is only ~10,000 calls/day total, which materially constrains real-time sync, ETL backfills, and analytics use cases for any high-volume integration helpdesk.fiixsoftware.com
API access is gated to the Enterprise plan only, Lite, Basic, and Professional tenants must upgrade before any programmatic integration is possible, raising the floor cost of any Fiix-connected product helpdesk.fiixsoftware.com
The API is explicitly not RESTful and not SOAP, it is a Fiix-specific JSON-over-HTTP RPC calling convention, which means generic REST/OpenAPI tooling, code generators, and HTTP-client integrations do not work cleanly without writing Fiix-specific wrappers fiixlabs.github.io
Authentication is a three-key (Application Key + Access Key + Secret Key) static-credential model with no OAuth 2.0, there is no app-marketplace style consent flow, no token refresh, and no scoped permissions, so credentials must be provisioned and rotated manually per tenant fiixlabs.github.io
v6 schema migration breaks API symmetry, v6 Work Orders and v6 Equipment have no API path to v5 Work Orders / v5 Equipment, so integrators have to reason about which schema version each customer is on and handle both helpdesk.fiixsoftware.com
Reporting and bulk data export via the API and reporting module is cited as cumbersome, many customers resort to scheduled CSV exports rather than API-driven extracts, limiting the realistic shape of downstream analytics integrations capterra.com
SDKs are limited to Java and JavaScript (https://github.com/fiixlabs), no official Python, Go, Ruby, .NET, or PHP SDKs, so most modern data-engineering stacks have to consume the raw JSON RPC surface directly github.com
There is no public sandbox tenant, no anonymous developer signup, and no OpenAPI/Swagger interactive console, integrators have to obtain credentials from a paying customer's Enterprise tenant before they can meaningfully build, blocking horizontal multi-tenant integrators from prototyping fiixlabs.github.io
Customers report being told they cannot downgrade from a premium subscription tier to a more basic one, with limited flexibility, and that escalation paths have resulted in being blocked rather than resolved g2.com
Reporting module is frequently described as complex to customize and limited for non-trivial custom reports, exporting data and configuring report options is a recurring source of frustration capterra.com
Pricing is reported as more expensive than several competing CMMS options, with explicit customer commentary about switching to eMaint or Limble for better customization and value limble.com
Inability to customize certain data-analysis flows and limitations like inability to add multiple BOMs per asset are cited as feature gaps for asset-heavy operations g2.com
Implementation can hit technical issues that take a long time to resolve, particularly for multi-site or ERP-integrated rollouts capterra.com
Work order default settings require repeated manual adjustment, creating friction in day-to-day technician workflows g2.com
Mobile experience relies on a mobile-optimized web client rather than a fully native, polished app, competitors like UpKeep and MaintainX are routinely cited as having a more refined technician mobile UX task360.app
Gartner Peer Insights and Software Advice reviewers cite reporting limitations and integration challenges as the two most consistent areas where Fiix underperforms vs. expectations gartner.com