/api/public/v1/build-deploymentsList recent deployments
The deployment stream — the newest Vercel deployments of the platform and portals projects, merged and newest first, as Builder’s Deployments page shows them. Every branch push, not only Builder’s. `state` is Vercel’s lifecycle word; a row still building has `buildingAt` and a null `durationMs`, and `inspectorUrl` is its build logs. Read live from Vercel, so there is no paging; `configured` is false where the Vercel API is off, as it is in development. Engineers only.
Required scope
The access token must carry this scope. A token missing it gets 403 Forbidden. Grant them to an API client under Dev Tools → API, to an assistant or CLI sign-in when you approve or edit it under Dev Tools, and to a teammate under Employee → Permissions.
curl -X GET "https://www.pxb.app/api/public/v1/build-deployments" \
-H "Authorization: Bearer your_access_token"{
"message": "Deployments retrieved successfully!",
"content": {
"deployments": [
{
"uid": "dpl_4Q7m2k1p",
"name": "platform",
"project": "platform",
"url": "https://platform-4q7m2k1p-pixelbase.vercel.app",
"inspectorUrl": "https://vercel.com/pixelbase/platform/4Q7m2k1p",
"state": "BUILDING",
"target": "preview",
"branch": "builder/eng-214-session-status-over-mcp",
"branchUrl": "https://github.com/pixelbase-inc/web/tree/builder/eng-214-session-status-over-mcp",
"commitSha": "6ca6db8",
"commitUrl": "https://github.com/pixelbase-inc/web/commit/6ca6db8",
"commitMessage": "feat(mcp): builder sessions and their status as tools",
"creator": "bronsonberwald",
"creatorAvatarUrl": "https://github.com/bronsonberwald.png?size=48",
"createdAt": 1791650000000,
"buildingAt": 1791650062000,
"durationMs": null
}
],
"configured": true
}
}In the console
The same thing done by hand, for anyone comparing the API against the screen they already use.