Limble CMMS
Limble CMMS is a cloud-based computerized maintenance management system (CMMS) for manufacturing, facilities, and fleet maintenance teams. The Limble REST API V2 provides programmatic access to assets, locations, work orders, preventive maintenance schedules, parts inventory, purchase orders, vendors, users, and webhooks across regionally distributed endpoints covering North America, Canada, Australia, and Europe.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Limble CMMS the way a machine reads it — 77 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Limble CMMS scores 41.8/100 (developing), with a separate agent-readiness read of 27/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Limble CMMS's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/limble-cmms/"
title="Limble CMMS on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/limble-cmms.svg"
alt="Limble CMMS Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/limble-cmms/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/limble-cmms/"
title="Limble CMMS on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/limble-cmms/card.svg"
alt="Limble CMMS Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Limble CMMS
Each block below is one kind of artifact we hold for Limble CMMS. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 2
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Limble API V2
The Limble CMMS REST API V2 provides HTTPS access to maintenance management data including assets, locations, work orders, preventive maintenance tasks, parts, purchase orders, ...
Limble CMMS Routes API
The Routes API from Limble CMMS — 120 operation(s) for routes.
Open Collections 43
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONLimble API V2 Assets API
OPEN COLLECTIONLimble API V2 Assets Batch API
OPEN COLLECTIONLimble API V2 Assets Bills API
OPEN COLLECTIONLimble API V2 Assets Budgets API
OPEN COLLECTIONLimble API V2 Assets Capacity API
OPEN COLLECTIONLimble API V2 Assets Categories API
OPEN COLLECTIONLimble API V2 Assets Comments API
OPEN COLLECTIONLimble API V2 Assets Exceptions API
OPEN COLLECTIONLimble API V2 Assets Fields API
OPEN COLLECTIONLimble API V2 Assets Files API
OPEN COLLECTIONLimble API V2 Assets General Ledgers API
OPEN COLLECTIONLimble API V2 Assets Image API
OPEN COLLECTIONLimble API V2 Assets Images API
OPEN COLLECTIONLimble API V2 Assets Instructions API
OPEN COLLECTIONLimble API V2 Assets Invoices API
OPEN COLLECTIONLimble API V2 Assets Items API
OPEN COLLECTIONLimble API V2 Assets Labor API
OPEN COLLECTIONLimble API V2 Assets Locations API
OPEN COLLECTIONLimble API V2 Assets Logs API
OPEN COLLECTIONLimble API V2 Assets Me API
OPEN COLLECTIONLimble API V2 Assets Options API
OPEN COLLECTIONLimble API V2 Assets Parts API
OPEN COLLECTIONLimble API V2 Assets Priorities API
OPEN COLLECTIONLimble API V2 Assets Purchasables API
OPEN COLLECTIONLimble API V2 Assets Purchase Orders API
OPEN COLLECTIONLimble API V2 Assets Regions API
OPEN COLLECTIONLimble API V2 Assets Roles API
OPEN COLLECTIONLimble API V2 Assets Routes API
OPEN COLLECTIONLimble API V2 Assets Schedules API
OPEN COLLECTIONLimble API V2 Assets State API
OPEN COLLECTIONLimble API V2 Assets Statuses API
OPEN COLLECTIONLimble API V2 Assets Steps API
OPEN COLLECTIONLimble API V2 Assets Tags API
OPEN COLLECTIONLimble API V2 Assets Tasks API
OPEN COLLECTIONLimble API V2 Assets Teams API
OPEN COLLECTIONLimble API V2 Assets Transactions API
OPEN COLLECTIONLimble API V2 Assets Units of Measure API
OPEN COLLECTIONLimble API V2 Assets Users API
OPEN COLLECTIONLimble API V2 Assets Vendor Associations API
OPEN COLLECTIONLimble API V2 Assets Vendors API
OPEN COLLECTIONLimble API V2 Assets Webhooks API
OPEN COLLECTIONLimble API V2 Assets Work Request Submissions API
OPEN COLLECTIONScroll within the panel for all 43 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Limble Cmms Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Limble CMMS API Rules
SPECTRALLimble CMMS API Rules
SPECTRALJSON Schema 8
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Asset
JSON SCHEMALocation
JSON SCHEMAPart
JSON SCHEMAPurchaseOrder
JSON SCHEMATask
JSON SCHEMAUser
JSON SCHEMAVendor
JSON SCHEMAWorkRequestSubmission
JSON SCHEMAScroll within the panel for all 8 ·
JSON Structure 8
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Limble Cmms Asset Structure
JSON STRUCTURELimble Cmms Location Structure
JSON STRUCTURELimble Cmms Part Structure
JSON STRUCTURELimble Cmms Purchase Order Structure
JSON STRUCTURELimble Cmms Task Structure
JSON STRUCTURELimble Cmms User Structure
JSON STRUCTURELimble Cmms Vendor Structure
JSON STRUCTURELimble Cmms Work Request Submission Structure
JSON STRUCTUREScroll within the panel for all 8 ·
Examples 9
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 9 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Limble CMMS — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 3
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Commercial 1
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/limble-cmms · machine-readable index on apis.io
This is an independent, third-party profile of Limble CMMS, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.