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

The Folders API from Luminance — 10 operation(s) for folders.

Luminance Folders API is one of 21 APIs that Luminance publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Folders. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

20 operations 10 paths 6 schemas 4 DELETE9 GET4 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 Folders 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 20

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

Folders 20
GET
/projects/{project-id}/folders
Get Folder Collection
6 params → 200401403405422429500
POST
/projects/{project-id}/folders
Create a folder
1 param body → 201401403405422429500
PATCH
/projects/{project-id}/folders
Patch information on a Folder Collection
6 params body → 200401403405422429500
GET
/projects/{project-id}/folders/{folder-id}
Get Information on a Single Folder
2 params → 200401403405422429500
PATCH
/projects/{project-id}/folders/{folder-id}
Modify Information on a Single Folder
3 params body → 200401403405422429500
GET
/api2/projects/{project_id}/folders
List folders
6 params → 200
POST
/api2/projects/{project_id}/folders
Create folder
1 param body → 201
PATCH
/api2/projects/{project_id}/folders
Update folders by filter
6 params body → 200
DELETE
/api2/projects/{project_id}/folders
Delete folders by filter
6 params → 204
GET
/api2/projects/{project_id}/folders/{folder_id}
Get folder
2 params → 200
PATCH
/api2/projects/{project_id}/folders/{folder_id}
Update folder
2 params body → 200
DELETE
/api2/projects/{project_id}/folders/{folder_id}
Delete folder
2 params → 204
POST
/api2/projects/{project_id}/folders/{folder_id}/upload
Upload a document into a folder
7 params body → 200201422
GET
/api2/projects/{project_id}/folders/{folder_id}/documents
List documents in folder
2 params → 200
DELETE
/api2/projects/{project_id}/folders/{folder_id}/documents
Delete documents in folder by filter
2 params → 204
GET
/api2/projects/{project_id}/folders/{folder_id}/documents/{document_id}
Get document in folder
3 params → 200404
DELETE
/api2/projects/{project_id}/folders/{folder_id}/documents/{document_id}
Delete document in folder
3 params → 204
GET
/api2/projects/{project_id}/folders/{folder_id}/documents/{document_id}/annotations
List document annotations (folder-scoped path)
3 params → 200
GET
/api2/projects/{project_id}/folders/{folder_id}/documents/{document_id}/annotations/annotationText
Retrieve annotation text (folder-scoped path)
5 params → 200
GET
/api2/projects/{project_id}/folders/{folder_id}/documents/{document_id}/download
Download document file (folder-scoped path)
4 params → 200404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Document (12 properties), Folder (9 properties), Folder_3 (8 properties), Folder_2 (8 properties). Each schema is shown below with its type and property counts.

Folder
object
9 properties
FolderPatch
object
4 properties
FolderPost
object
3 properties 2 required
Document
object
Document object (see API2Schema documents table)
12 properties
Folder_2
object
Folder object (see API2Schema folders table)
8 properties
Folder_3
object
Folder object (see API2Schema folders table)
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

luminance-folders-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 Matter Versions API
Luminance Matters API
Luminance Project Users API
Luminance Projects API
Where this information came from

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