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

The Vendors API from Limble CMMS — 11 operation(s) for vendors.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

This API exposes 18 operations across 11 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.

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

Paths & Operations 18

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

Vendors 18
GET
/v2/vendors/fields
Vendor Fields
getVendorsFields 10 params → 200400401403429500
POST
/v2/vendors/fields
New Vendor Suggested Field
postVendorsFields → 201400401403409429500
GET
/v2/vendors/fields/suggested
Vendor Suggested Fields
getVendorsFieldsSuggested 4 params → 200400401403429500
PATCH
/v2/vendors/fields/{valueID}
Update Vendor Field Value
patchVendorsFieldsByValueID 1 param → 200400401403404409429500
DELETE
/v2/vendors/fields/{valueID}
Delete Vendor Field
deleteVendorsFieldsByValueID 1 param → 200400401403404429500
PUT
/v2/vendors/{vendorID}/fields
Attach Field to Vendor
putVendorsByVendorIDFields 1 param → 201400401403404409429500
PUT
/v2/vendors/{vendorID}/image
Add Vendor Image
putVendorsByVendorIDImage 1 param → 200400401403404409429500
DELETE
/v2/vendors/{vendorID}/image
Delete Vendor Image
deleteVendorsByVendorIDImage 1 param → 200400401403404429500
DELETE
/v2/vendors/logs/file/{fileID}
Delete Vendor Log File
deleteVendorsLogsFileByFileID 1 param → 200400401403404429500
PUT
/v2/vendors/{vendorID}/logs/{logID}/file
Add Vendor Log File
putVendorsByVendorIDLogsByLogIDFile 2 params → 200400401403404409429500
GET
/v2/vendors/{vendorID}/logs
Vendor Logs
getVendorsByVendorIDLogs 9 params → 200400401403404429500
POST
/v2/vendors/{vendorID}/logs
New Vendor Log
postVendorsByVendorIDLogs 1 param body → 201400401403404409429500
PATCH
/v2/vendors/logs/{logID}
Update Vendor Log
patchVendorsLogsByLogID 1 param body → 200400401403404409429500
DELETE
/v2/vendors/logs/{logID}
Delete Vendor Log
deleteVendorsLogsByLogID 1 param → 200400401403404429500
GET
/v2/vendors
Vendors
getVendors 8 params → 200400401403429500
POST
/v2/vendors
New Vendor
postVendors → 201400401403409429500
PATCH
/v2/vendors/{vendorID}
Update Vendor
patchVendorsByVendorID 1 param → 200400401403404409429500
DELETE
/v2/vendors/{vendorID}
Delete Vendor
deleteVendorsByVendorID 1 param → 200400401403404429500

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Vendor (11 properties), LogEntry (5 properties). Each schema is shown below with its type and property counts.

Vendor
object
11 properties
LogEntry
object
5 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-vendors-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
#Vendors
← Back to L APIs
API Details
ID
limble-cmms:limble-cmms-vendors-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-vendors-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/limble-cmms-vendors-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 Vendors 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.