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

Luminance Tasks API

The Tasks API from Luminance — 14 operation(s) for tasks.

Luminance Tasks API is one of 21 APIs that Luminance 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 and API documentation.

This API exposes 19 operations across 14 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://{moniker}.app.luminance.com.

19 operations 14 paths 2 schemas 2 DELETE12 GET2 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://your-instance.app.luminance.com/api2
Authentication
OAuth 2.0, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Luminance Tasks API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2) using the clientCredentials flow. It accepts HTTP bearer tokens (JWT) (bearerAuth).

  • bearerAuth — Access token from the OAuth2 client credentials flow. See the Authentication section above for how to obtain a token (curl to your instance token endpoint); th…

Paths & Operations 19

Across 14 paths, the API surfaces 19 operations — 2 DELETE, 12 GET, 2 PATCH, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Tasks 19
GET
/projects/{project-id}/tasks
Get a list of tasks in a particular project, including alerts and knowledge banks
9 params → 200401403405422429500
GET
/projects/{project-id}/tasks/{task-id}
Get information on a specific task, including alerts and knowledge banks
2 params → 200401403405422429500
POST
/projects/{project-id}/tasks/knowledge_bank_from_template
Create a new criteria-based Knowledge Bank by specifying a document to create knowledge bank positions from and a contract type for that document, resulting in a precedent type task being created for…
2 params body → 200401403405422429500
GET
/api2/projects/{project_id}/tasks
List tasks (including Knowledge Banks)
1 param → 200
GET
/api2/projects/{project_id}/tasks/{task_id}
Get task
2 params → 200
POST
/api2/projects/{project_id}/tasks/knowledge_bank_from_template
Create Knowledge Bank from template and generate positions
1 param body → 202422
GET
/api2/projects/{project_id}/tasks/{task_id}/reviews
List task reviews
2 params → 200
POST
/api2/projects/{project_id}/tasks/{task_id}/reviews
Create task review
2 params body → 201
PATCH
/api2/projects/{project_id}/tasks/{task_id}/reviews
Update multiple task reviews by filter
2 params body → 200
GET
/api2/projects/{project_id}/tasks/{task_id}/reviews/{review_id}
Get task review
3 params → 200
PATCH
/api2/projects/{project_id}/tasks/{task_id}/reviews/{review_id}
Update task review
3 params body → 200
GET
/api2/projects/{project_id}/tasks/{task_id}/reviews/{review_id}/analysis
Get task review analysis results
3 params → 200
GET
/api2/projects/{project_id}/tasks/{task_id}/reviews/documents
List documents for task reviews
2 params → 200
DELETE
/api2/projects/{project_id}/tasks/{task_id}/reviews/documents
Delete multiple documents in task reviews
2 params → 204
GET
/api2/projects/{project_id}/tasks/{task_id}/reviews/documents/{document_id}
Get document in task review
3 params → 200404
DELETE
/api2/projects/{project_id}/tasks/{task_id}/reviews/documents/{document_id}
Delete document in task review
3 params → 204
GET
/api2/projects/{project_id}/tasks/{task_id}/reviews/documents/{document_id}/download
Download document file (task review path)
3 params → 200404
GET
/api2/projects/{project_id}/tasks/{task_id}/reviews/documents/{document_id}/annotations
List document annotations (task review path)
3 params → 200
GET
/api2/projects/{project_id}/tasks/{task_id}/reviews/documents/{document_id}/annotations/annotationText
Retrieve annotation text (task review path)
5 params → 200

Schemas 2

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

KnowledgeBankFromTemplate
object
Payload necessary to create a knowledge bank from a specified document ID of the specified contract type
4 properties
Task
object
15 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

luminance-tasks-api-openapi.yml Raw ↑

Other APIs Luminance publishes across the network.

Luminance Accounts API
Luminance Annotation Source Relations API
Luminance Annotation Sources API
Luminance Annotation Types API
Luminance Annotations API
Luminance Contract Creation API
Luminance Document Templates API
Luminance Documents API
Luminance Folders API
Luminance Matter Versions API
Luminance Matters API
Luminance Project Users API
Where this information came from

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