List chat documents
List documents attached to an Extract chat.
is_linked=true). Filter with has_schema and processing_status.Authorizations
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
Query Parameters
Only docs with / without a pinned schema.
Sort field: ±created_at / ±file_name. Default -created_at.
Filter by processing status: pending / completed / failed.
Response
Lynx processing pipeline status: pending → completed/failed
pending- Pendingcompleted- Completedfailed- Failed
pending, completed, failed Processing completion percentage 0-100
Current processing stage name, or the failure reason on a FAILED attachment
Number of pages in the original document
True when a schema (StructVersion) is pinned for extraction.
StructVersion that produced this attachment's extraction_result. NULL for non-batch attachments or pre-versioning records.
ISO language code for translation target (e.g. 'en', 'ar')
Whether this attachment came from Knowledge Base
Original Knowledge Base file ID if from KB
Lynx document ID after processing (extraction + chunking + indexing)
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.

