Get Machine user Key By ID
Get a specific Key of a machine user by its id. Machine keys are used to authenticate with jwt profile authentication.
Path Parameters
- userId string required
- keyId string required
Header Parameters
- x-zitadel-orgid string
The default is always the organization of the requesting user. If you like to get a user from another organization include the header. Make sure the requesting user has permission in the requested organization.
Responses
- 200
- default
OK
- application/json
- application/grpc
- application/grpc-web+proto
- Schema
- Example (from schema)
Schema
key object
{
"key": {
"id": "69629023906488334",
"details": {
"sequence": "2",
"creationDate": "2023-05-12",
"changeDate": "2023-05-12",
"resourceOwner": "69629023906488334"
},
"type": "KEY_TYPE_JSON",
"expirationDate": "3019-04-01T08:45:00.000000Z"
}
}
- Schema
- Example (from schema)
Schema
key object
{
"key": {
"id": "69629023906488334",
"details": {
"sequence": "2",
"creationDate": "2023-05-12",
"changeDate": "2023-05-12",
"resourceOwner": "69629023906488334"
},
"type": "KEY_TYPE_JSON",
"expirationDate": "3019-04-01T08:45:00.000000Z"
}
}
- Schema
- Example (from schema)
Schema
key object
{
"key": {
"id": "69629023906488334",
"details": {
"sequence": "2",
"creationDate": "2023-05-12",
"changeDate": "2023-05-12",
"resourceOwner": "69629023906488334"
},
"type": "KEY_TYPE_JSON",
"expirationDate": "3019-04-01T08:45:00.000000Z"
}
}
An unexpected error response.
- application/json
- application/grpc
- application/grpc-web+proto
- Schema
- Example (from schema)
Schema
- code int32
- message string
details object[]
{
"code": 0,
"message": "string",
"details": [
{
"@type": "string"
}
]
}
- Schema
- Example (from schema)
Schema
- code int32
- message string
details object[]
{
"code": 0,
"message": "string",
"details": [
{
"@type": "string"
}
]
}
- Schema
- Example (from schema)
Schema
- code int32
- message string
details object[]
{
"code": 0,
"message": "string",
"details": [
{
"@type": "string"
}
]
}
GET /users/:userId/keys/:keyId
Authorization
type: oauth2flow: authorizationCodescopes: openid,urn:zitadel:iam:org:project:id:zitadel:aud
Request
Request
curl -L -X GET 'https://$ZITADEL_DOMAIN/management/v1/users/:userId/keys/:keyId' \
-H 'Accept: application/json' \
-H 'Authorization: Bearer <TOKEN>'
curl -L -X GET 'https://$ZITADEL_DOMAIN/management/v1/users/:userId/keys/:keyId' \
-H 'Accept: application/json' \
-H 'Authorization: Bearer <TOKEN>'
curl -L -X GET 'https://$ZITADEL_DOMAIN/management/v1/users/:userId/keys/:keyId' \
-H 'Accept: application/json' \
-H 'Authorization: Bearer <TOKEN>'
curl -L -X GET 'https://$ZITADEL_DOMAIN/management/v1/users/:userId/keys/:keyId' \
-H 'Accept: application/json' \
-H 'Authorization: Bearer <TOKEN>'
curl -L -X GET 'https://$ZITADEL_DOMAIN/management/v1/users/:userId/keys/:keyId' \
-H 'Accept: application/json' \
-H 'Authorization: Bearer <TOKEN>'
curl -L -X GET 'https://$ZITADEL_DOMAIN/management/v1/users/:userId/keys/:keyId' \
-H 'Accept: application/json' \
-H 'Authorization: Bearer <TOKEN>'
curl -L -X GET 'https://$ZITADEL_DOMAIN/management/v1/users/:userId/keys/:keyId' \
-H 'Accept: application/json' \
-H 'Authorization: Bearer <TOKEN>'