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

Lucid Document Comments API

Retrieve comment threads on a document, list comments within a thread, and post new comments to an existing thread.

Lucid Document Comments API is one of 37 APIs that Lucid publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Document Comments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

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

Requests are made against a single base URL, https://api.lucid.co.

3 operations 2 paths 4 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.lucid.co
Authentication
OAuth 2.0, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Lucid Document Comments API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 142 scopes. It accepts HTTP bearer tokens (ApiKey).

Paths & Operations 3

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

Document Comments 3

Retrieve comment threads on a document, list comments within a thread, and post new comments to an existing thread.

GET
/v1/documents/{documentId}/threads
List Document Threads
listDocumentThreads 1 param → 200400403
GET
/v1/documents/{documentId}/threads/{threadId}/comments
List Thread Comments
listDocumentThreadComments 2 params → 200400403404
POST
/v1/documents/{documentId}/threads/{threadId}/comments
Post Thread Comment
postDocumentThreadComment 2 params body → 204400403404

Schemas 4

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

PostCommentRequestBody
object
Request body for posting a comment to a thread.
1 property 1 required
DocumentComment
object
A comment within a comment thread on a document.
5 properties 4 required
DocumentThread
object
A comment thread on a document.
3 properties 3 required
ThreadStatus
string
The status of a comment thread. OPEN indicates an unresolved thread, CLOSED indicates a resolved thread.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lucid-document-comments-api-openapi.yml Raw ↑

Other APIs Lucid publishes across the network.

Lucid MCP Server
Lucid Accounts API
Lucid Audit Logs API
Lucid Cloud API
Lucid Collection API
Lucid Collection Properties API
Lucid Create Diagram API
Lucid Data Item API
Lucid Data Set API
Lucid Data Set Grant API
Lucid Data Set Properties API
Lucid Data Source API
Where this information came from

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