Skip to main content
The Trunk Merge Queue API picks up two new endpoints, a newly-documented list endpoint, and additional fields across ten existing endpoints.

​
New endpoints

/getSubmittedPullRequests — the batch form of /getSubmittedPullRequest. Look up many PRs in a single request. Unsubmitted PRs come back in a notFound list rather than failing the whole request. /listMergeQueueTestingResults — list completed merge queue testing runs over a time range, newest first. Pass any returned testRunId to /getMergeQueueTestingDetails for the full record.

​
Now in the reference

/listPullRequests now has its own reference page. The endpoint itself shipped in March (see the original announcement); it just wasn’t in the navigation until now. If you’re choosing between the three read endpoints, the API landing page has a short guide: use /getSubmittedPullRequest(s) when you already know which PRs to look up, and /listPullRequests to discover them with cursor pagination and state or concluded-time filters.

​
Expanded fields on existing endpoints

  • /getSubmittedPullRequest accepts an optional includeTimeline flag. When set, the response includes every state change with its cause: cancellation reasons, branch-protection block reasons, the culprit for conflicts, and failing checks.
  • /listPullRequests accepts an until bound on the concluded-time range.
  • /getQueue and /updateQueue expose allowedBotSubmitters, stateLabelsEnabled, testBranchConstructionMode, and notReadyTimeoutHours. pendingFailureDepth and testingTimeoutMinutes now accept 0 to disable.
  • /getMergeQueueTestingDetails reports the PENDING, WAITING, and REQUESTED deployment-gate check states.
  • Flaky Tests list endpoints now include bazel_label on test cases.
No endpoints or schemas were removed.