Knowledge
List documents
Paginate through every document record in the workspace, with filters on source, title, URL, linked article, and linked operation.
GET
Returns document records in the workspace tied to your API key, ordered byDocumentation Index
Fetch the complete documentation index at: https://docs.usefini.com/llms.txt
Use this file to discover all available pages before exploring further.
updatedAt descending then externalId descending. Use it to enumerate documents, inspect ingestion status, and find document IDs to pass back to Queue ingestion.
Headers
Bearer token containing your Fini workspace API key. Format:
Bearer fini_...Query parameters
Maximum number of documents to return.
Document ID to paginate from. Use the last document’s
id from the previous response to fetch the next page, or the first document’s id to fetch the previous page.Pagination direction when a cursor is supplied. Note the inverted mapping:
next moves toward older documents; previous moves back toward newer ones. This is because results are sorted by updatedAt descending.Optional document-source filter. Supported values:
web, files, googledrive, zendesk, notion, confluence.Optional English-processing filter.
Exact document ID filter.
Case-insensitive partial match on the document title.
Case-insensitive partial match on the original source URL.
Filter by linked article or knowledge node ID.
Filter by linked knowledge operation. Supported values:
ADD_ARTICLE_TO_FOLDER, CREATE_SUBFOLDER_AND_ARTICLE, UPDATE_ARTICLE, DO_NOTHING.Return only linked documents flagged as changed.
The response includes
hasMore but not a nextCursor field. Use the last (or first) document’s id from the returned array as the cursor for the next call.Response
Array of document records.
Whether more results exist beyond the current page.
Pagination
Cursor pagination uses document IDs directly:- pass the last document’s
idfrom the previous response withdirection=nextto move toward older documents - pass the first document’s
idwithdirection=previousto move back toward newer documents
cursor, the API starts from the most recently updated documents.
Errors
400 Bad Request
400 Bad Request
Query parameters are invalid. Common causes: unsupported
source value, unsupported linkedOperation value, malformed UUID in id or articleId.401 Unauthorized
401 Unauthorized
403 Forbidden
403 Forbidden
The API key doesn’t include the
read scope, or it’s scoped to a different workspace.The response is an empty documents array
The response is an empty documents array
Either the workspace has no documents matching your filters, or no documents at all. Drop filters one at a time to confirm which one is excluding results.

