How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Limble CMMS Items API

The Items API from Limble CMMS — 3 operation(s) for items.

Limble CMMS Items API is one of 43 APIs that Limble CMMS publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Item. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 3 paths, and defines 2 schemas. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against 5 base URLs: https://api.limblecmms.com, https://ca-api.limblecmms.com, https://au-api.limblecmms.com, https://eu-api.limblecmms.com, https://21cfr-api.limblecmms.com.

5 operations 3 paths 2 schemas 1 DELETE1 GET1 PATCH1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
https://api.limblecmms.com
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Limble CMMS Items API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (BasicAuth). By default, every request must be authenticated.

Paths & Operations 5

Across 3 paths, the API surfaces 5 operations — 1 DELETE, 1 GET, 1 PATCH, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Items 5
GET
/v2/po/items
Get Purchase Order Items
getPoItems 7 params → 200400401403429500
POST
/v2/po/{poID}/items
New Purchase Order Item
postPoByPoIDItems 1 param body → 201400401403404409429500
PATCH
/v2/po/{poID}/items/{poItemID}
Update Purchase Order Item
patchPoByPoIDItemsByPoItemID 2 params body → 200400401403404409429500
DELETE
/v2/po/{poID}/items/{poItemID}
Delete PO Item
deletePoByPoIDItemsByPoItemID 2 params → 200400401403404429500
PUT
/v2/po/{poID}/items/{poItemID}
Receive PO Item
putPoByPoIDItemsByPoItemID 2 params body → 200400401403404409429500

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed is POItem (18 properties). Each schema is shown below with its type and property counts.

ErrorResponse
Error response body. The API emits two shapes today: the standard { message } shape returned by the central error handler and most controllers, and the legacy…
POItem
object
18 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

limble-cmms-items-api-openapi.yml Raw ↑

Other APIs Limble CMMS publishes across the network.

Limble API V2
Limble CMMS Assets API
Limble CMMS Batch API
Limble CMMS Bills API
Limble CMMS Budgets API
Limble CMMS Capacity API
Limble CMMS Categories API
Limble CMMS Comments API
Limble CMMS Exceptions API
Limble CMMS Fields API
Limble CMMS Files API
Limble CMMS General Ledgers API
Where this information came from

This is an independent, third-party profile of Limble CMMS Items API, 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.