Hanzo
OpenapiIam

(re)generates the target user's key of the requested TYPE and returns it once,… — POST /v1/iam/users/{owner}/{name}/keys

(re)generates the target user's key of the requested TYPE and returns it once, over the shared authorizeMinter + mintTarget seam.

POST /v1/iam/users/{owner}/{name}/keys

Addresshttps://api.hanzo.ai/v1/iam/users/{owner}/{name}/keys
MethodPOST
Operationpost_iam_users_by_owner_by_name_keys
AuthAuthorization: Bearer $HANZO_API_KEY

(re)generates the target user's key of the requested TYPE and returns it once, over the shared authorizeMinter + mintTarget seam. ?type=secret (the default) yields the confidential sk-; ?type=publishable yields the pk- that is safe to ship in client JS and resolves to an org, never a principal.

It writes the schema.Key row that the resolvers actually read. schema.User.AccessKey is not a credential and nothing resolves it, so a key stamped there would authenticate nobody.

Request

2 fields.

FieldInTypeRequiredDescription
ownerpathstringyes
namepathstringyes

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