Skip to main content
GET
/
v1
/
pipelines
/
executions
/
{pipeline_execution_id}
/
status
Get pipeline execution status
curl --request GET \
  --url https://api.dune.com/api/v1/pipelines/executions/{pipeline_execution_id}/status \
  --header 'X-Dune-Api-Key: <x-dune-api-key>'
{
  "error": "<string>",
  "node_executions": [
    {
      "id": 123,
      "materialized_view_refresh_status": {
        "error": "<string>",
        "execution_id": "<string>",
        "name": "<string>",
        "status": "<string>"
      },
      "query_execution_status": {
        "error": "<string>",
        "execution_id": "<string>",
        "query_id": 123,
        "status": "<string>"
      }
    }
  ],
  "status": "<string>"
}
This endpoint retrieves the status of a pipeline execution, including the status of each node (query or materialized view refresh) in the pipeline.

​
Understanding Pipeline Status

A pipeline execution contains multiple nodes, each representing either:
  • Query Execution: A query that’s part of the pipeline
  • Materialized View Refresh: A materialized view that’s refreshed as part of the pipeline
Each node has its own status and can be tracked independently.

​
Pipeline States

The overall pipeline can be in one of the following states:
  • pending: Pipeline execution has been queued but not yet started
  • executing: Pipeline is currently running
  • completed: All nodes in the pipeline have completed successfully

​
Node Status

Each node in the pipeline includes:
  • node_id: Unique identifier for the node
  • status: Current state of the node execution
  • query_execution_status or materialized_view_refresh_status: Detailed status information

​
Response Structure

The 200 response includes:
  • status: Overall pipeline execution status (pending, executing, or completed)
  • node_executions: Array of individual node executions with their status and results

​
Example Usage

# Check pipeline status
curl "https://api.dune.com/api/v1/pipelines/executions/01HZABC123.../status" \
  -H "X-Dune-Api-Key: YOUR_API_KEY"
Poll this endpoint periodically to monitor pipeline execution progress. Each node’s status will update as the pipeline progresses through its execution.

​
Monitoring Pipeline Progress

You can use this endpoint to:
  • Track which nodes have completed and which are still running
  • Identify any nodes that have failed
  • Retrieve execution IDs for individual queries to fetch their results
  • Monitor overall pipeline health
Once a pipeline execution completes, you can retrieve the results of individual queries using their respective execution IDs from the node status.

Headers

​
X-Dune-Api-Key
string
required

API Key for the service

Path Parameters

​
pipeline_execution_id
string
required

Unique identifier of the pipeline execution

Query Parameters

​
api_key
string

Alternative to using the X-Dune-Api-Key header

Response

OK

​
error
string

Error message if the pipeline execution failed

​
node_executions
object[]

List of node executions in the pipeline.

​
status
string

Overall status of the pipeline execution