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

The Assets API from Limble CMMS — 15 operation(s) for assets.

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

This API exposes 22 operations across 15 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.

22 operations 15 paths 4 schemas 5 DELETE6 GET4 PATCH4 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 Assets API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (BasicAuth). By default, every request must be authenticated.

Paths & Operations 22

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

Assets 22
PUT
/v2/assets/{assetID}/image
Add Asset Main Image
putAssetsByAssetIDImage 1 param → 200400401403404409429500
DELETE
/v2/assets/{assetID}/image
Delete Asset Main Image
deleteAssetsByAssetIDImage 1 param → 200400401403404429500
GET
/v2/assets/fields
Asset Fields
getAssetsFields 14 params → 200400401403429500
POST
/v2/assets/fields
New Asset Suggested Field
postAssetsFields → 201400401403409429500
GET
/v2/assets/fields/suggested
Asset Suggested Fields
getAssetsFieldsSuggested 5 params → 200400401403429500
GET
/v2/assets/fields/history
Asset Field History
getAssetsFieldsHistory 6 params → 200400401403429500
PUT
/v2/assets/{assetID}/fields
Attach Field to Asset
putAssetsByAssetIDFields 1 param → 200400401403404409429500
DELETE
/v2/assets/fields/{valueID}
Delete Asset Field
deleteAssetsFieldsByValueID 1 param → 200400401403404429500
PATCH
/v2/assets/fields/{valueID}
Update Asset Field Value
patchAssetsFieldsByValueID 1 param → 200400401403404409429500
DELETE
/v2/assets/logs/file/{fileID}
Delete Asset Log File
deleteAssetsLogsFileByFileID 1 param → 200400401403404429500
PUT
/v2/assets/{assetID}/logs/{logID}/file
Add Asset Log File
putAssetsByAssetIDLogsByLogIDFile 2 params → 200400401403404409429500
GET
/v2/assets/{assetID}/logs
Asset Logs
getAssetsByAssetIDLogs 9 params → 200400401403404429500
POST
/v2/assets/{assetID}/logs
New Asset Log
postAssetsByAssetIDLogs 1 param body → 201400401403404409429500
PATCH
/v2/assets/logs/{logID}
Update Asset Log
patchAssetsLogsByLogID 1 param body → 200400401403404409429500
DELETE
/v2/assets/logs/{logID}
Delete Asset Log
deleteAssetsLogsByLogID 1 param → 200400401403404429500
POST
/v2/assets/fields/batch/update
Batch Update Asset Fields
postAssetsFieldsBatchUpdate body → 200400401403409429500
GET
/v2/assets/parts
Asset Parts
getAssetsParts 8 params → 200400401403429500
GET
/v2/assets
Assets
getAssets 11 params → 200400401403429500
POST
/v2/assets
New Asset
postAssets → 201400401403409429500
DELETE
/v2/assets/{assetID}
Delete Asset
deleteAssetsByAssetID 1 param → 200400401403429500
PATCH
/v2/assets/{assetID}
Patch Asset
patchAssetsByAssetID 1 param → 200400401403404409429500
PATCH
/v2/assets/{assetID}/move
Move Asset to another Location
patchAssetsByAssetIDMove 1 param body → 200400401403404409429500

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Asset (10 properties), AssetPart (7 properties), LogEntry (5 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…
AssetPart
object
7 properties
LogEntry
object
5 properties
Asset
object
10 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Limble CMMS publishes across the network.

Limble API V2
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
Limble CMMS Image API
Where this information came from

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