BeeBridge AIBeeBridge AI
API Reference
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.

Revoke the legacy PAT during transition

Requires an access_token.revoke proof with exactly {"legacy": true} as context. The legacy PAT may no longer exist after retirement.

DELETE
/api/user/access_tokens/legacy
AuthorizationBearer <token>

Use the session access_token returned by password or OAuth sign-in. A PAT cannot manage or create PATs.

In: header

Header Parameters

X-Security-Proofstring

Short-lived, single-use security proof bound to the current identity and exact operation. It is neither a PAT nor a model API key.

Response Body

application/json

application/json

application/json

application/json

application/json

curl -X DELETE "https://api.beeaicloud.com/api/user/access_tokens/legacy" \  -H "X-Security-Proof: string"
{
  "success": true,
  "message": "string",
  "data": null
}
{
  "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?

Revoke the legacy PAT during transition | BeeBridge AI