GET /api/v2/api-keys/admin/personal-keyslists every Personal key and host sign-in in the deployment withapikeys:readat platform scope. A row never names its owner and never carries a key’s secret or hash.POST /api/v2/api-keys/admin/personal-keys/revokerevokes any person’s Personal key withapikeys:manageat platform scope and tells the owner, as the Console does. A missing or non-Personal key answers404; an already revoked key answers409.- A Personal key’s audit rows now record who decided the change: a revoke through the API records a platform key as a system actor and a Personal key as its owner. The Console’s own rows are unchanged. Both routes are reachable from MCP through
forge_call_operationin thegovernancetool group.
GET /api/v2/planning/admin/my-blockersandGET /api/v2/planning/admin/could-helprun the Blueprint’s two person views for a Personal key, which acts as its owner; any other key is refused with403andpersonRequired: true. Each lists only ordinary project tasks whose project the key may read (projects:readat the project’s home), names no assignee, and sayspartialwhen a bound ran out. See My blocked tasks.GET /api/v2/people/admin/integrity/findingslists a workforce integrity run’s findings, at most five a page, optionally of one classification or status, withworkforce:read. A finding answers its invariant, classification, status, decision and the ids it affects; its key, evidence, resolved names, proposed repair and decision reason stay in the Console, since they can name a person. See People and members.
GET /api/v2/costs/admin/limits/alllists every scope’s spending limits a page at a time, withcost:readat platform scope. A limit never answers its scope id.GET /api/v2/costs/admin/budgets/treereads the budget hierarchy as a tree of up to 200 budgets, and refuses a larger hierarchy with409 conflictrather than answer part of it. It answers each budget’s period spend, burn rate, days until exhausted and triggered alert count.- The Console’s emergency-stop switches still list every limit, and its budget analytics tree is refused past 200 budgets, as the route is. See Costs and budgets.
POST /api/v2/files/admin/chat-attachment-contentanswers the bytes (base64) of one of a chat channel’s attachments withchat:readat the channel’s home. It never answers a download URL. An attachment the channel attachments list leaves out answers404, and a file of more than 4,000,000 bytes answers409.- The read is recorded under the key, or a Personal key’s owner, before any byte is read. See Files.
- A Console dashboard widget now shows its data only to a viewer who holds, at the platform scope, the permission the Console’s own page for that data needs:
cost:readfor spend and tokens,workflows:readfor active runs,audit:readfor interventions,factories:readfor active factories andagents:readfor agent completions. The Morning Briefing needs all four ofcost:read,workflows:read,audit:readandagents:read. A viewer without the permission sees the widget’s empty state. Before this change any signed-in person could read these deployment-wide figures by adding the widget to their own dashboard. - When a widget’s data source changes, the data fetched for the old source is cleared; the widget shows its empty state until the next scheduled refresh, within 15 minutes, or its refresh button. Display-only edits keep the data.
- Active-run and agent-completion widgets now show run content masked, as the Runs and Delegated work pages do.
- See Forge Console for the default widgets.
GET /api/v2/external-apps/admin/owned-agentslists the agents an External App owns, newest first, withapps:readat platform scope. It answers only agents homed where the key also holdsagents:read, and leaves the app’s users’ Personal Agents out, as on every agent route.- See External apps.
POST /api/v2/filestakes optionalscopeType,scopeEntityIdandsourcequery parameters. A named scope binds the upload to that knowledge scope, the binding a Console upload makes, beside its binding to the credential’s org unit.- A named scope also needs
files:writeat the scope’s home (the deployment root for a scope with no org-unit, factory or project home); without it the upload answers403and nothing is stored. A scope naming a top-level org unit also makes the file readable in that org tree. An upload withoutscopeTypeis unchanged. See Binding an upload to a scope.
GET /api/v2/models/admin/catalog/list-with-usagelists catalog models a page at a time (agents:read), with the Console’s search, provider, status, group and sort filters. Each model carriesagentCountandassignedAgents: only agents the key may read, never a personal or unhomed agent.- Each page takes
limit(at most 100) andcursor, and answersmeta.hasMoreandmeta.nextCursor. See Models.
GET /api/v2/notifications/admin/event-typeslists every notification event type with its per-channel delivery and which channels have a provider. It needs all ofaudit:read,grants:readandpolicies:readat platform scope, as the Console’s event matrix does; a key missing any one gets403naming it. See Notifications.- An admin route’s
403now names the permission the request was refused on. Before, a route that needs more than one permission always named its first.
GET /api/v2/notifications/admin/slack-sendslists the most recent outbound Slack sends withaudit:readat platform scope. A send never answers its channel or its error text.- The route is reachable from MCP through
forge_call_operationin thegovernancetool group. See Notifications.
GET /api/v2/api-keys/admin/own-keyslists your own Personal keys and host sign-ins, active and revoked.POST /api/v2/api-keys/admin/own-keys/revokerevokes one of your keys; an already revoked key answers409.POST /api/v2/api-keys/admin/own-keys/deletedeletes one of your revoked keys and disables its role grants; an active key answers409.- They need no permission, only a Personal key whose own scopes reach
apikeys:read(list) orapikeys:manage(revoke and delete); otherwise403names that key. They act only on your own keys: another person’s key, a missing key and a non-Personal key answer404. Any credential but a Personal key gets403withpersonRequired: true. A revoke or delete is audited as you, through your Personal key. All three are reachable from MCP throughforge_call_operationin thegovernancetool group.
- Deciding whether a person is in a machine caller’s reach reads each of their worker seats. A person with more seats and assignments than one request can read used to fail the request on the platform’s read limit. Single reads and writes now answer that person exactly as one out of reach: the same
404, and nothing is written. A workforce repair applied through the API stopsBLOCKEDwithREPAIR_OUT_OF_REACH. - The member, external tool identity and worker lists end a page before such a person and return them at the start of the next page, so nobody in reach is left out. Only a person still too large at the start of a page is omitted.
POST /api/v2/workforce/createPersonandPOST /api/v2/people/admin/workers/createfail as before (500) when the email belongs to such a person, and write nothing.
GET /api/v2/connections/admin/external-tools/identityreads one external tool identity, andPOST .../identity/update,.../identity/statusand.../identity/verifyrename it, change its scopes or status, and probe it against its provider, withplatform:manageat platform scope. An identity never answers its credential.- An identity owned by a person a key may not reach (a person seated in or under a customer organization) answers 404, as a missing one does, and is never changed or probed. See Connections.
GET /api/v2/people/admin/memberslists members a page at a time (grants:read): each person’s seats, emails and whether their sign-in is linked.GET /api/v2/connections/admin/external-tools/identitiesand.../identities/by-principallist external tool identities a page at a time (platform:manageat platform scope), without their credentials.- Each page takes
limit(at most 50) andcursor, and answersmeta.hasMoreandmeta.nextCursor. A person a key may not reach (seated in or under a customer organization), and an identity they own, is left out of the page, and a page also ends early when reading more people would exceed its read limits, so a page may be shorter thanlimitwhilemeta.hasMoreis true. See People and Connections.
POST /api/v2/people/admin/integrity/repairs/applyapplies a previewed workforce repair run whose plan hash still matches (workforce:manage).- A run whose plan names a person a key may not reach (seated in or under a customer organization), or a seat, position or org unit placed in or under a customer organization, answers 404, as a missing run does, and is left unchanged.
- The repair runs on the scheduler after the call returns. Before each step that writes, it checks reach again. If anything in its plan has left the key’s reach since it was applied, the run stops with status
BLOCKEDand error codeREPAIR_OUT_OF_REACH, and that step writes nothing. See People.

