Skip to content
Connect an agent
Organisations

Reveal an organisation API key

Shows the full value of one of the organisation's keys again, to the owner or an admin.

POST/orgs/{org}/keys/{id}/reveal

TL;DR

QuestionAnswer
What does it do?Reveal an organisation API key.
What does it take?org, id in the path.
What does it return?Status 200 with a body of type RevealedApiKey.
What can go wrong?401 not signed in; 403 a member may not reveal keys (orgs.forbidden), or the request came from an origin that may not make changes; 404 no such organisation or key, or the caller is not a member of the organisation; 409 this key has no sealed copy to show; 429 too many requests; 503 revealing keys is not set up on this server, or organisations are not. Every failure uses the one error envelope.

What it does

Shows the full value of one of the organisation's keys again, to the owner or an admin. Only a key with a sealed copy can be revealed. Audited by key id, never by value.

Path parameters

FieldTypeRequiredDescription
orgstringyesThe organisation's id or its slug.
idstringyes

Responses

StatusMeaningBody
200The key, with its full value.RevealedApiKey
401Not signed in.ErrorResponse
403A member may not reveal keys (orgs.forbidden), or the request came from an origin that may not make changes.ErrorResponse
404No such organisation or key, or the caller is not a member of the organisation.ErrorResponse
409This key has no sealed copy to show.ErrorResponse
429Too many requests.ErrorResponse
503Revealing keys is not set up on this server, or organisations are not.ErrorResponse

Response body

A 200 answer has the type RevealedApiKey.

FieldTypeRequiredDescription
idstringyes
keystringyesThe full key.

See also

DocWhy
API referenceEvery endpoint, and the error envelope
SchemasEvery request and response type
Tool referenceThe operations as callable tools