Update a service account.
PUT/api/admin/service-account/:id
Updates an existing service account identified by its id.
Request
Path Parameters
- application/json
Body
required
#/components/schemas/updateServiceAccountSchema
The name of the service account
Service Account 1The id of the root role for the service account
1Describes the properties required to update a service account
Responses
- 200
- 400
- 401
- 403
- 404
- 415
#/components/schemas/serviceAccountSchema
- application/json
- Schema
- Example (from schema)
Schema
Array [
]
The service account id
54321Deprecated: for internal use only, should not be exposed through the API
falseThe name of the service account
My Service AccountDeprecated: service accounts don't have emails associated with them
noemail@getunleash.ioThe service account username
my-service-accountThe service account image url
https://example.com/my-service-account.pngDeprecated: service accounts cannot be invited via an invitation link
https://example.com/invite-linkDeprecated: service accounts cannot log in to Unleash
0Deprecated: internal use only
falseThe root role id associated with the service account
1Deprecated. This property is always null. To find out when a service account was last seen, check its tokens list and refer to each token's lastSeen property instead.
nullThe service account creation date
2021-01-01T00:00:00.000Ztokens
object[]
The list of tokens associated with the service account
The PAT's ID. PAT IDs are incrementing integers. In other words, a more recently created PAT will always have a higher ID than an older one.
Possible values: >= 1
1The token used for authentication. It is automatically generated by Unleash when the PAT is created and that is the only time this property is returned.
user:xyzrandomstringThe date and time of when the PAT was created.
2023-04-19T08:15:14.000ZWhen the PAT was last seen/used to authenticate with. null if it has not been used yet.
2023-04-19T08:15:14.000ZThe ID of the user this PAT belongs to.
1337The PAT's description.
user:xyzrandomstringThe PAT's expiration date.
2023-04-19T08:15:14.000Z{
"id": 54321,
"name": "My Service Account",
"username": "my-service-account",
"imageUrl": "https://example.com/my-service-account.png",
"rootRole": 1,
"createdAt": "2021-01-01T00:00:00.000Z",
"tokens": [
{
"id": 1,
"secret": "user:xyzrandomstring",
"createdAt": "2023-04-19T08:15:14.000Z",
"seenAt": "2023-04-19T08:15:14.000Z",
"userId": 1337,
"description": "user:xyzrandomstring",
"expiresAt": "2023-04-19T08:15:14.000Z"
}
]
}
The request data does not match what we expect.
- application/json
- Schema
- Example (from schema)
Schema
The ID of the error instance
9c40958a-daac-400e-98fb-3bb438567008The name of the error kind
ValidationErrorA description of what went wrong.
The request payload you provided doesn't conform to the schema. The .parameters property should be object. You sent [].{
"id": "9c40958a-daac-400e-98fb-3bb438567008",
"name": "ValidationError",
"message": "The request payload you provided doesn't conform to the schema. The .parameters property should be object. You sent []."
}
Authorization information is missing or invalid. Provide a valid API token as the authorization header, e.g. authorization:*.*.my-admin-token.
- application/json
- Schema
- Example (from schema)
Schema
The ID of the error instance
9c40958a-daac-400e-98fb-3bb438567008The name of the error kind
AuthenticationRequiredA description of what went wrong.
You must log in to use Unleash. Your request had no authorization header, so we could not authorize you. Try logging in at /auth/simple/login.{
"id": "9c40958a-daac-400e-98fb-3bb438567008",
"name": "AuthenticationRequired",
"message": "You must log in to use Unleash. Your request had no authorization header, so we could not authorize you. Try logging in at /auth/simple/login."
}
The provided user credentials are valid, but the user does not have the necessary permissions to perform this operation
- application/json
- Schema
- Example (from schema)
Schema
The ID of the error instance
9c40958a-daac-400e-98fb-3bb438567008The name of the error kind
NoAccessErrorA description of what went wrong.
You need the "UPDATE_ADDON" permission to perform this action in the "development" environment.{
"id": "9c40958a-daac-400e-98fb-3bb438567008",
"name": "NoAccessError",
"message": "You need the \"UPDATE_ADDON\" permission to perform this action in the \"development\" environment."
}
The requested resource was not found.
- application/json
- Schema
- Example (from schema)
Schema
The ID of the error instance
9c40958a-daac-400e-98fb-3bb438567008The name of the error kind
NotFoundErrorA description of what went wrong.
Could not find the addon with ID "12345".{
"id": "9c40958a-daac-400e-98fb-3bb438567008",
"name": "NotFoundError",
"message": "Could not find the addon with ID \"12345\"."
}
The operation does not support request payloads of the provided type. Please ensure that you're using one of the listed payload types and that you have specified the right content type in the "content-type" header.
- application/json
- Schema
- Example (from schema)
Schema
The ID of the error instance
9c40958a-daac-400e-98fb-3bb438567008The name of the error kind
ContentTypeerrorA description of what went wrong.
We do not accept the content-type you provided (application/xml). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format.{
"id": "9c40958a-daac-400e-98fb-3bb438567008",
"name": "ContentTypeerror",
"message": "We do not accept the content-type you provided (application/xml). Try using one of the content-types we do accept instead (application/json) and make sure the body is in the corresponding format."
}