Get Current Identity

Use Case

Use this endpoint to identify the bot user associated with the current token and to inspect the effective capabilities of that token.

Endpoint

Permissions

Requires a valid Bearer token. No additional scope is required.

Response Example

{
  "object": "bot_user",
  "id": "aaaaaaaa-aaaa-4aaa-8aaa-aaaaaaaaaaaa",
  "name": "My Integration",
  "workspace_id": "99999999-9999-4999-8999-999999999999",
  "workspace_name": "Team Workspace",
  "owner": {
    "object": "user",
    "id": "bbbbbbbb-bbbb-4bbb-8bbb-bbbbbbbbbbbb"
  },
  "capabilities": {
    "pages.read": true,
    "pages.write": true,
    "blocks.read": true,
    "blocks.write": true,
    "databases.read": true,
    "databases.write": true,
    "users.read": true,
    "users.email.read": false,
    "search.read": true
  },
  "type": "integration",
  "integration_id": "77777777-7777-4777-8777-777777777777"
}

Behavior

• The response is the API identity for the token, not the profile of the integration creator.
• OAuth tokens return the scopes authorized for that token.
• Use capabilities to decide which UI actions or background jobs to enable.

Errors

• 401 unauthorized: missing, invalid, or expired token.

Related Docs

Prerequisites

• Make Your First Request

Next Steps

• Get User

References

• Object Models
• Scope Reference