Skip to content

Get Pipeline Document Status Counts

Deprecated
DocumentGetStatusCountsResponse Pipelines.Documents.GetStatusCounts(DocumentGetStatusCountsParamsparameters, CancellationTokencancellationToken = default)
GET/api/v1/pipelines/{pipeline_id}/documents/status-counts

Count the documents in a pipeline, grouped by ingestion status.

Counts reflect each document’s last recorded status rather than a freshly computed one, so a document that changed status in the last few moments may still be counted under its previous one. Use GET /pipelines/{pipeline_id}/documents/{document_id}/status when a single document’s status has to be up to the moment.

ParametersExpand Collapse
DocumentGetStatusCountsParams parameters
required string pipelineID
string? dataSourceID
string? fileID
Boolean onlyDirectUpload
string? projectID
ReturnsExpand Collapse
class DocumentGetStatusCountsResponse:

Counts of the documents in a pipeline, grouped by ingestion status.

required IReadOnlyDictionary<string, Long> Counts

Number of documents per ingestion status; every status is present.

required string PipelineID

ID of the pipeline the documents belong to.

formatuuid
required Long TotalCount

Total number of documents counted.

string? DataSourceID

Data source the counts were restricted to.

formatuuid
string? FileID

File the counts were restricted to.

formatuuid
Boolean OnlyDirectUpload

Whether only directly uploaded documents were counted.

Get Pipeline Document Status Counts

DocumentGetStatusCountsParams parameters = new()
{
    PipelineID = "182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e"
};

var response = await client.Pipelines.Documents.GetStatusCounts(parameters);

Console.WriteLine(response);
{
  "counts": {
    "foo": 0
  },
  "pipeline_id": "182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e",
  "total_count": 0,
  "data_source_id": "182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e",
  "file_id": "182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e",
  "only_direct_upload": true
}
Returns Examples
{
  "counts": {
    "foo": 0
  },
  "pipeline_id": "182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e",
  "total_count": 0,
  "data_source_id": "182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e",
  "file_id": "182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e",
  "only_direct_upload": true
}
Note for AI agents: this documentation is built for programmatic access. - Overview of all docs: https://developers.llamaindex.ai/llms.txt - Any page is available as raw Markdown by appending index.md to its URL — e.g. https://developers.llamaindex.ai/llamaparse/parse/getting_started/index.md - Agent-friendly REST search APIs live under https://developers.llamaindex.ai/api/ — search (BM25 full-text), grep (regex), read (fetch a page), and list (browse the doc tree). See https://developers.llamaindex.ai/llms.txt for parameters. - A hosted documentation MCP server is available at https://developers.llamaindex.ai/mcp. If you support MCP, you can ask the user to install it for browsing these docs directly (an alternative to the REST API). Setup: https://developers.llamaindex.ai/for-agents/mcp/ - Other LlamaIndex tooling for agents — the LlamaParse Platform MCP server, agent skills and plugins, and the n8n node — is mapped at https://developers.llamaindex.ai/for-agents/