Skip to main content
GET
List a chat's documents
Home uploads and linked documents (is_linked=true). Filter with has_schema and processing_status.

Authorizations

Authorization
string
header
required

Organisation API key from Settings → API / /api/keys/. The secret is shown once. Send Authorization: Bearer sk-abacus-…. One active key per organisation. Ingest (/api/v2/ingest/*) refuses API keys — that surface is Auth0-only with ingest:read / ingest:write scopes.

Path Parameters

thread_id
string
required

Query Parameters

has_schema
boolean

Only docs with / without a pinned schema.

order
string

Sort field: ±created_at / ±file_name. Default -created_at.

processing_status
string

Filter by processing status: pending / completed / failed.

Response

id
integer
required
read-only
file_name
string
required
read-only
file_type
string
required
read-only
processing_status
enum<string>
required

Lynx processing pipeline status: pending → completed/failed

  • pending - Pending
  • completed - Completed
  • failed - Failed
Available options:
pending,
completed,
failed
processing_progress
integer
required
read-only

Processing completion percentage 0-100

processing_stage
string
required
read-only

Current processing stage name, or the failure reason on a FAILED attachment

page_count
integer
required
read-only

Number of pages in the original document

has_schema
boolean
required
read-only

True when a schema (StructVersion) is pinned for extraction.

extraction_struct_version_id
integer | null
required
read-only

StructVersion that produced this attachment's extraction_result. NULL for non-batch attachments or pre-versioning records.

target_language
string
required
read-only

ISO language code for translation target (e.g. 'en', 'ar')

is_from_kb
boolean
required
read-only

Whether this attachment came from Knowledge Base

kb_file_id
integer | null
required
read-only

Original Knowledge Base file ID if from KB

lynx_document_id
string | null
required
read-only

Lynx document ID after processing (extraction + chunking + indexing)

is_linked
boolean
required
read-only

True when the doc is linked into context['chat_pk'] from elsewhere.

A direct (home) attachment has chat_id == chat_pk; a linked-in doc keeps its original home chat_id (the link lives in ChatAttachmentLink), so chat_id != chat_pk marks it linked.

created_at
string<date-time>
required
read-only