List system keys
const url = 'https://example.com/v1/system/keys';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/v1/system/keys \ --header 'Authorization: Bearer <token>'The operator’s system keys (kgi_sy_…): each acts in no tenant, for one service, with the scopes it was minted with. Newest first, revoked ones too. Never returns secrets. Only the full system capability (kindgi:system: the deployment’s own token, or a full system key) lists them; on a runtime serving one tenant, the deployment’s own token alone.
Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”The system keys.
object
A system key (kgi_sy_…): the operator’s, acting in no tenant. Never its secret.
object
The key’s id.
What the key is for, as given at mint.
Who minted it: a system key’s id, or boot for the deployment’s own token.
Example
{ "data": [ { "scopes": [ "system:tenants" ] } ]}Missing / malformed / expired / revoked bearer token.
object
object
Stable machine-readable discriminant. Values match domain error codes (see docs/API-ROUTE-CONVENTIONS.md §4.3).
Optional, kind-specific.
object
Server-assigned request id; also echoed via X-Request-Id header.
Examplegenerated
{ "error": { "code": "example", "message": "example", "details": {}, "requestId": "example" }}A tenant’s key or session (system-principal-required), or a scoped system key (system-scope-missing; on a runtime serving one tenant, system-key-scope-not-served for one holding anything but system:license).
object
object
Stable machine-readable discriminant. Values match domain error codes (see docs/API-ROUTE-CONVENTIONS.md §4.3).
Optional, kind-specific.
object
Server-assigned request id; also echoed via X-Request-Id header.
Examplegenerated
{ "error": { "code": "example", "message": "example", "details": {}, "requestId": "example" }}