Current actor
Explain one of your refusals
A Platform API credential explains a 403 it received, by the decisionId the refusal named, without the governance evidence permissions. Requires no permission.
GET
Explain one of the calling credential's own refusals
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.
v2 compatibility notes
When Forge refuses a request with403, the error names a decisionId: the refusal Forge recorded.
GET /api/v2/me/denials/{decisionId} explains that refusal to the credential it refused. It needs
none of the permissions
GET /api/v2/governance/explainDecision requires, which a
refused caller usually lacks.
Authorization
The endpoint requires no permission, and explains only your own refusals. Forge records every Platform API refusal against the credential that made the request, and answers only when that recorded credential is the one calling now:- A platform or Personal key reads its own refusals.
- An External App reads the refusals its access tokens received. Refusals of its static companion key are a different credential’s, and the other way round.
404 with code
resource_missing, so the endpoint never tells you whether someone else’s decision exists. A path that
names no well-formed id, or a request with a query parameter or a body, is refused with 400.
Response
The answer is what the refusal already told you, plus the recorded gate. It never names another
actor, a role, a grant, a policy, or the request’s free-text detail.
Example
Related
- List your effective permissions
- Errors — the
403envelope and itsdecisionId

