Hanzo
OpenapiIam

Resolve a PUBLISHABLE key to the organization that owns it

Answers which organization a publishable key belongs to — what a service calls to attribute a request that arrived carrying a key shipped in a browser.

GET /v1/iam/keys/org

Addresshttps://api.hanzo.ai/v1/iam/keys/org
MethodGET
Operationget_iam_keys_org
AuthAuthorization: Bearer $HANZO_API_KEY

Answers which organization a publishable key belongs to — what a service calls to attribute a request that arrived carrying a key shipped in a browser. This is the noun spelling of /v1/iam/resolve-key, the same handler at the address that replaces it; both answer while callers migrate.

It names an ORGANIZATION and never a person. No path through it loads or returns a user, so a key placed in client code cannot become a way to learn who anyone is — which is the whole reason this is a separate door from the one below.

A key that is expired, secret rather than publishable, or simply unknown all answer with the same sentence and a code saying which it was. Only a confidential service that has already proved it may resolve keys reads that code — there is no anonymous caller here to probe which keys exist — and telling those apart is what lets a holder be told to re-mint an expired key instead of hunting a configuration error.

Request

GET /v1/iam/keys/org takes no parameters and no body — the credential is the whole request.

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.

Examples

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.


IAM API · All Hanzo APIs · Interactive reference

How is this guide?

On this page