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 Parts API

The Parts API from Limble CMMS — 20 operation(s) for parts.

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

This API exposes 31 operations across 20 paths, and defines 4 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.

31 operations 20 paths 4 schemas 7 DELETE12 GET4 PATCH5 POST3 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 Parts API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (BasicAuth). By default, every request must be authenticated.

Paths & Operations 31

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

Parts 31
GET
/v2/assets/parts
Asset Parts
getAssetsParts 8 params → 200400401403429500
PUT
/v2/parts/{partID}/image
Add Part Image
putPartsByPartIDImage 1 param → 200400401403404409429500
DELETE
/v2/parts/{partID}/image
Delete Part Image
deletePartsByPartIDImage 1 param → 200400401403404429500
POST
/v2/parts/categories
Create Part Category
postPartsCategories → 201400401403409429500
GET
/v2/parts/categories
Get Categories
getPartsCategories 2 params → 200400401403429500
PATCH
/v2/parts/categories/{categoryID}
Update Part Category
patchPartsCategoriesByCategoryID 1 param → 200400401403404409429500
DELETE
/v2/parts/categories/{categoryID}
Delete Part Category
deletePartsCategoriesByCategoryID 1 param → 200400401403404429500
GET
/v2/parts/fields
Part Fields
getPartsFields 11 params → 200400401403429500
POST
/v2/parts/fields
New Part Suggested Field
postPartsFields → 201400401403409429500
GET
/v2/parts/fields/suggested
Part Suggested Fields
getPartsFieldsSuggested 4 params → 200400401403429500
PATCH
/v2/parts/fields/{valueID}
Update Part Field Value
patchPartsFieldsByValueID 1 param → 200400401403404409429500
DELETE
/v2/parts/fields/{valueID}
Delete Part Field
deletePartsFieldsByValueID 1 param → 200400401403404429500
PUT
/v2/parts/{partID}/fields
Attach Field to Part
putPartsByPartIDFields 1 param → 201400401403404409429500
GET
/v2/parts/{partID}/logs
Part Logs
getPartsByPartIDLogs 10 params → 200400401403404429500
POST
/v2/parts/{partID}/logs
New Part Log
postPartsByPartIDLogs 1 param body → 201400401403404409429500
PATCH
/v2/parts/logs/{logID}
Update Part Log
patchPartsLogsByLogID 1 param body → 200400401403404409429500
DELETE
/v2/parts/logs/{logID}
Delete Part Log
deletePartsLogsByLogID 1 param → 200400401403404429500
GET
/v2/parts/logs
All Part Logs
getPartsLogs 10 params → 200400401403429500
GET
/v2/parts/{partID}/purchasables
Get Purchasables
getPartsByPartIDPurchasables 4 params → 200400401403404429500
GET
/v2/parts/vendors/associations
Get Part Vendor Associations
getPartsVendorsAssociations 10 params → 200400401403429500
POST
/v2/parts/vendors/associations
Create Part Vendor Association
postPartsVendorsAssociations body → 201400401403404409429500
DELETE
/v2/parts/vendors/associations/{relationID}
Delete Part Vendor Association
deletePartsVendorsAssociationsByRelationID 1 param → 204400401403404429500
GET
/v2/parts
Parts
getParts 9 params → 200400401403429500
POST
/v2/parts
Create Part
postParts → 201400401403409429500
PATCH
/v2/parts/{partID}
Update Part
patchPartsByPartID 1 param → 200400401403404409429500
DELETE
/v2/parts/{partID}
Delete Part
deletePartsByPartID 1 param → 200400401403404429500
GET
/v2/parts/usage
Parts Usage
getPartsUsage 7 params → 200400401403429500
GET
/v2/tasks/{taskID}/parts
Get attached parts
getTasksByTaskIDParts 1 param → 200400401403404429500
PUT
/v2/tasks/{taskID}/parts
Attach part to task
putTasksByTaskIDParts 1 param → 200400401403404409429500
GET
/v2/tasks/parts
Get all attached parts
getTasksParts 4 params → 200400401403429500
DELETE
/v2/tasks/{taskID}/{partID}
Delete part from task
deleteTasksByTaskIDByPartID 2 params → 200400401403404429500

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Part (21 properties), AssetPart (7 properties), PartLogEntry (7 properties). Each schema is shown below with its type and property counts.

PartLogEntry
object
7 properties
AssetPart
object
7 properties
Part
object
21 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…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

limble-cmms-parts-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 Parts 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.