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

The Tasks API from Limble CMMS — 24 operation(s) for tasks.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

This API exposes 39 operations across 24 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.

39 operations 24 paths 4 schemas 9 DELETE13 GET4 PATCH7 POST6 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 Tasks API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (BasicAuth). By default, every request must be authenticated.

Paths & Operations 39

Across 24 paths, the API surfaces 39 operations — 9 DELETE, 13 GET, 4 PATCH, 7 POST, 6 PUT. Each is listed below with its method, path, parameters, and response codes.

Tasks 39
PUT
/v2/tasks/{taskID}/invoices/{invoiceID}/file
Attach a file to an invoice
putTasksByTaskIDInvoicesByInvoiceIDFile 2 params → 200400401403404409429500
DELETE
/v2/tasks/{taskID}/invoices/{invoiceID}/file
Delete file from Invoice
deleteTasksByTaskIDInvoicesByInvoiceIDFile 2 params → 200400401403404429500
GET
/v2/tasks/invoices
Invoices
getTasksInvoices 6 params → 200400401403429500
PUT
/v2/tasks/{taskID}/invoices
Attach an Invoice to task
putTasksByTaskIDInvoices 1 param body → 200400401403404409429500
DELETE
/v2/tasks/{taskID}/invoices/{invoiceID}
Delete invoice from task
deleteTasksByTaskIDInvoicesByInvoiceID 2 params → 200400401403404429500
PATCH
/v2/tasks/{taskID}/invoices/{invoiceID}
Update an Invoice
patchTasksByTaskIDInvoicesByInvoiceID 2 params body → 200400401403404409429500
GET
/v2/tasks/{taskID}/instructions/{instructionID}/options
Instruction Options
getTasksByTaskIDInstructionsByInstructionIDOptions 2 params → 200400401403404429500
POST
/v2/tasks/{taskID}/instructions/{instructionID}/options
New Instruction Option
postTasksByTaskIDInstructionsByInstructionIDOptions 2 params body → 201400401403404409429500
DELETE
/v2/tasks/instructions/{instructionID}/options/{instructionOptionID}
Delete Instruction Option
deleteTasksInstructionsByInstructionIDOptionsByInstructionOptionID 2 params → 200400401403404429500
PATCH
/v2/tasks/instructions/{instructionID}/options/{instructionOptionID}
Update Instruction Option
patchTasksInstructionsByInstructionIDOptionsByInstructionOptionID 2 params body → 200400401403404409429500
GET
/v2/tasks/{taskID}/instructions
Task Instructions
getTasksByTaskIDInstructions 4 params → 200400401403404429500
POST
/v2/tasks/{taskID}/instructions
New Task Instruction
postTasksByTaskIDInstructions 1 param → 201400401403404409429500
PATCH
/v2/tasks/instructions/{instructionID}
Update Task Instruction
patchTasksInstructionsByInstructionID 1 param → 200400401403404409429500
DELETE
/v2/tasks/instructions/{instructionID}
Delete Task Instruction
deleteTasksInstructionsByInstructionID 1 param → 200400401403404429500
GET
/v2/tasks/instructions/{instructionID}
Get Task Instruction by ID
getTasksInstructionsByInstructionID 1 param → 200400401403404429500
GET
/v2/tasks/instructions
Batch Task Instructions
getTasksInstructions 3 params → 200400401403429500
PUT
/v2/tasks/instructions/{instructionID}/image
Task Instruction Image
putTasksInstructionsByInstructionIDImage 1 param → 200400401403404409429500
DELETE
/v2/tasks/instructions/{instructionID}/image
Delete Task Instruction Image
deleteTasksInstructionsByInstructionIDImage 2 params → 200400401403404429500
PUT
/v2/tasks/{taskID}/image
Upload Task Main Image
putTasksByTaskIDImage 1 param → 200400401403404409429500
DELETE
/v2/tasks/{taskID}/image
Delete Task Main Image
deleteTasksByTaskIDImage 1 param → 200400401403404429500
GET
/v2/tasks/labor
Task Labor
getTasksLabor 8 params → 200400401403429500
GET
/v2/tasks/labor/categories
Get Labor Categories
getTasksLaborCategories 3 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
GET
/v2/tasks/{taskID}/comments
Task Comments
getTasksByTaskIDComments 3 params → 200400401403404429500
POST
/v2/tasks/{taskID}/comments
Add Task Comments
postTasksByTaskIDComments 1 param body → 200400401403404409429500
GET
/v2/tasks/{taskID}/tags
Tags
getTasksByTaskIDTags 1 param → 200400401403404429500
PUT
/v2/tasks/{taskID}/tags
PUT Apply Task Tags
putTasksByTaskIDTags 1 param → 200400401403404409429500
DELETE
/v2/tasks/{taskID}/tags/{tagRaw}
DELETE Remove Task Tag
deleteTasksByTaskIDTagsByTagRaw 2 params → 200400401403404429500
GET
/v2/work-requests/work-request-submissions
List WR Submissions
getWorkRequestsWorkRequestSubmissions 11 params → 200400401403429500
POST
/v2/work-requests/work-request-submissions
Create WR Submission
postWorkRequestsWorkRequestSubmissions body → 200400401403429500
POST
/v2/work-requests/work-request-submissions/{workRequestSubmissionID}/approve
Approve WR Submission
postWorkRequestSubmissionsApprove 1 param → 200400401403404429500
POST
/v2/work-requests/work-request-submissions/{workRequestSubmissionID}/decline
Decline WR Submission
postWorkRequestSubmissionsDecline 1 param body → 200400401403404429500
POST
/v2/tasks
New Task
postTasks 5 params body → 201400401403409429500
GET
/v2/tasks
Tasks
getTasks 25 params → 200400401403429500
PATCH
/v2/tasks/{taskID}
Update Task
patchTasksByTaskID 1 param → 200400401403404409429500
DELETE
/v2/tasks/{taskID}
Delete Task
deleteTasksByTaskID 1 param → 200400401403404429500

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Task (40 properties), WorkRequestSubmission (21 properties), TaskInstruction (8 properties). Each schema is shown below with its type and property counts.

WorkRequestSubmission
object
21 properties
Task
object
40 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…
TaskInstruction
object
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

limble-cmms-tasks-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
#Task
← Back to L APIs
API Details
ID
limble-cmms:limble-cmms-tasks-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-tasks-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/limble-cmms-tasks-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 Tasks 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.