Skip to main content
GET
Get a merge queue's dependency graph

Authorizations

Authorization
string
header
required

An API key, sent as Authorization: Bearer <key>. An organization admin creates one in the Trunk app under Settings → Developer → API Keys and chooses the merge-queue permissions it holds; a key with none can read merge queues but change nothing. Those permissions scope merge queue only: every key can use the Flaky Tests and Dynamic CI endpoints, including their writes, whatever permissions it holds.

Path Parameters

id
string
required

The merge queue's id.

Example:

"xK9mP2nQ"

Query Parameters

includeImpactedTargets
boolean
default:false

Include the impacted-target lists on nodes and edges. Off by default: resolving them costs one lookup per distinct commit in the graph.

Example:

false

Response

The queue's dependency graph

The queue's dependency graph. The dispatch order is NOT derivable from this — the engine schedules on a cascaded priority and a pending-failure gate, neither of which is in this payload; use GET /v2/merge-queues/{id}/order. It also contains only pull requests the engine has admitted to its graph, so anything awaiting admission, or not yet ready, is absent.

nodes
object[]
required
Maximum array length: 10000
edges
object[]
required

Transitively reduced, so an indirect dependency is represented through the node between its endpoints rather than as its own edge.

Maximum array length: 10000