Management APIManagement PAT integration and migration
⚠️Compliance notice: Use this project only for lawfully authorized API gateway, internal management, and private deployment scenarios. Follow upstream terms of service, platform rules, regulatory requirements, and content safety requirements.
Update a PAT name or permissions
name is required. Renaming alone needs no proof. Including scopes requires an access_token.update proof with exactly token_id and scopes in context.
AuthorizationBearer <token>
Use the session access_token returned by password or OAuth sign-in. A PAT cannot manage or create PATs.
In: header
Path Parameters
idinteger
Format
int64Range
1 <= valueHeader Parameters
X-Security-Proof?string
Short-lived, single-use security proof bound to the current identity and exact operation. It is neither a PAT nor a model API key.
namestring
Length
1 <= length <= 64scopes?array<string>
Permissions to grant to the PAT. Select from the current account catalog; a PAT cannot elevate the account.
Items
1 <= itemsResponse Body
application/json
application/json
application/json
application/json
application/json
curl -X PATCH "https://api.beeaicloud.com/api/user/access_tokens/1" \ -H "Content-Type: application/json" \ -d '{ "name": "string" }'{
"success": true,
"message": "string",
"data": {
"id": 0,
"name": "string",
"token_ref": "string",
"token_hint": "string",
"scopes": [
"string"
],
"expires_at": 0,
"created_at": 0,
"last_used_at": 0,
"last_used_ip": "string"
}
}{
"success": false,
"message": "string",
"code": "string",
"data": {
"code": "string"
}
}{
"success": false,
"message": "string",
"code": "string",
"data": {
"code": "string"
}
}{
"success": false,
"message": "string",
"code": "string",
"data": {
"code": "string"
}
}{
"success": false,
"message": "string",
"code": "string",
"data": {
"code": "string"
}
}How is this guide?