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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Limble CMMS

Limble CMMS Purchase Orders API

The Purchase Orders API from Limble CMMS — 10 operation(s) for purchase orders.

Documentation Provider Profile APIs.io OpenAPI GitHub

Limble CMMS Purchase Orders 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 Purchase Orders. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 16 operations across 10 paths, and defines 3 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.

16 operations 10 paths 3 schemas 4 DELETE4 GET3 PATCH3 POST2 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 Purchase Orders API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (BasicAuth). By default, every request must be authenticated.

Paths & Operations 16

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

Purchase Orders 16
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
GET
/v2/po/{poID}/comments
PO Comments
getPoByPoIDComments 3 params → 200400401403404429500
POST
/v2/po/{poID}/comments
Create PO Comment
postPoByPoIDComments 1 param → 201400401403404409429500
PUT
/v2/po/{poID}/comments/{commentID}/file
Upload PO Comment File
putPoByPoIDCommentsByCommentIDFile 2 params → 200400401403404409429500
DELETE
/v2/po/{poID}/comments/{commentID}/file
Delete PO Comment File
deletePoByPoIDCommentsByCommentIDFile 3 params → 200400401403404429500
DELETE
/v2/po/{poID}/comments/{commentID}
Delete PO Comment
deletePoByPoIDCommentsByCommentID 2 params → 200400401403404429500
PATCH
/v2/po/{poID}/state
Change PO State
patchPoByPoIDState 1 param → 200400401403404409429500
GET
/v2/po/{poID}/state/transitions
Get PO State Transitions
getPoByPoIDStateTransitions 1 param → 200400401403404429500
GET
/v2/po
Get Purchase Orders
getPo 10 params → 200400401403429500
POST
/v2/po
New Purchase Order
postPo body → 201400401403409429500
PATCH
/v2/po/{poID}
Update Purchase Order
patchPoByPoID 1 param body → 200400401403404409429500
DELETE
/v2/po/{poID}
Delete PO
deletePoByPoID 1 param → 200400401403404429500

Schemas 3

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

PurchaseOrder
object
27 properties
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-purchase-orders-api-openapi.yml Raw ↑

Other APIs Limble CMMS publishes across the network.

Limble API V2
AE Profile APIs.io
Limble CMMS Assets API
AE Profile APIs.io
Limble CMMS Batch API
AE Profile APIs.io
Limble CMMS Bills API
AE Profile APIs.io
Limble CMMS Budgets API
AE Profile APIs.io
Limble CMMS Capacity API
AE Profile APIs.io
Limble CMMS Categories API
AE Profile APIs.io
Limble CMMS Comments API
AE Profile APIs.io
Limble CMMS Exceptions API
AE Profile APIs.io
Limble CMMS Fields API
AE Profile APIs.io
Limble CMMS Files API
AE Profile APIs.io
Limble CMMS General Ledgers API
AE Profile APIs.io
#Purchase Orders
← Back to L APIs
API Details
ID
limble-cmms:limble-cmms-purchase-orders-api
Base URL
https://api.limblecmms.com
Docs
https://apidocs.limblecmms.com/
Provider
Limble CMMS
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=limble-cmms-purchase-orders-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/limble-cmms-purchase-orders-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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