Skip to content

Get Pipeline Document Status

Deprecated
ManagedIngestionStatusResponse Pipelines.Documents.GetStatus(DocumentGetStatusParamsparameters, CancellationTokencancellationToken = default)
GET/api/v1/pipelines/{pipeline_id}/documents/{document_id}/status

Return a single document for a pipeline.

ParametersExpand Collapse
DocumentGetStatusParams parameters
required string pipelineID
required string documentID
ReturnsExpand Collapse
class ManagedIngestionStatusResponse:
required Status Status

Status of the ingestion.

One of the following:
"CANCELLED"Cancelled
"ERROR"Error
"IN_PROGRESS"InProgress
"NOT_STARTED"NotStarted
"PARTIAL_SUCCESS"PartialSuccess
"SUCCESS"Success
DateTimeOffset? DeploymentDate

Date of the deployment.

formatdate-time
DateTimeOffset? EffectiveAt

When the status is effective

formatdate-time
IReadOnlyList<Error>? Error

List of errors that occurred during ingestion.

required string JobID

ID of the job that failed.

formatuuid
required string Message

List of errors that occurred during ingestion.

required Step Step

Name of the job that failed.

One of the following:
"DATA_SOURCE"DataSource
"FILE_UPDATER"FileUpdater
"INGESTION"Ingestion
"MANAGED_INGESTION"ManagedIngestion
"METADATA_UPDATE"MetadataUpdate
"PARSE"Parse
"TRANSFORM"Transform
string? JobID

ID of the latest job.

formatuuid

Get Pipeline Document Status

DocumentGetStatusParams parameters = new()
{
    PipelineID = "182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e",
    DocumentID = "document_id",
};

var managedIngestionStatusResponse = await client.Pipelines.Documents.GetStatus(parameters);

Console.WriteLine(managedIngestionStatusResponse);
{
  "status": "CANCELLED",
  "deployment_date": "2019-12-27T18:11:19.117Z",
  "effective_at": "2019-12-27T18:11:19.117Z",
  "error": [
    {
      "job_id": "182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e",
      "message": "message",
      "step": "DATA_SOURCE"
    }
  ],
  "job_id": "182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e"
}
Returns Examples
{
  "status": "CANCELLED",
  "deployment_date": "2019-12-27T18:11:19.117Z",
  "effective_at": "2019-12-27T18:11:19.117Z",
  "error": [
    {
      "job_id": "182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e",
      "message": "message",
      "step": "DATA_SOURCE"
    }
  ],
  "job_id": "182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e"
}
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/