GET
/
api
/
v1
/
get_user
curl --request GET \
  --url https://api.b-bot.space/api/v1/get_user \
  --header 'bbot-api-key: <api-key>'
[
  {
    "user": {
      "user_id": "google-oauth2|123456789012345678901",
      "email": "example.user@gmail.com",
      "given_name": "John",
      "email_verified": true,
      "updated_at": "2024-07-28T18:16:33.568Z",
      "identities": [
        {
          "access_token": "ya29.a0AXyoCgtJQY6FVBiPDTJq...",
          "expires_in": 3599,
          "connection": "google-oauth2",
          "user_id": "123456789012345678901",
          "provider": "google-oauth2",
          "isSocial": true
        }
      ],
      "created_at": "2024-03-18T17:08:05.432Z",
      "user_metadata": {
        "message_me": false,
        "newsletter": false,
        "api_keys": [
          "bbot_abcdefghij1234567890"
        ],
        "updates": false,
        "features": true,
        "apps": {},
        "tokens": 500,
        "follows_me": true,
        "mentions_me": true
      },
      "name": "John Doe",
      "nickname": "john.doe",
      "picture": "https://lh3.googleusercontent.com/a/ACg8ocL54DkmYmCmnGDiKfGJ2zv...",
      "family_name": "Doe",
      "last_login": "2024-07-28T18:16:16.163Z",
      "last_ip": "192.168.1.1",
      "logins_count": 125,
      "app_metadata": {}
    }
  }
]

The response provides comprehensive information about the authenticated user.

The timestamps are in ISO 8601 format.

The identities array contains details about the user’s authentication identities, including access tokens and their expiration.

The user_metadata and app_metadata objects can include various custom data associated with the user.

Authorizations

​
bbot-api-key
string
header
required

API key for authentication

Response

200
application/json

Get User response

The response is of type object[].