Skip to main content
POST
/
cabinet
/
auth
/
telegram
Auth Telegram
curl --request POST \
  --url https://api.example.com/cabinet/auth/telegram \
  --header 'Content-Type: application/json' \
  --data '
{
  "init_data": "<string>",
  "campaign_slug": "<string>",
  "referral_code": "<string>"
}
'
{
  "access_token": "<string>",
  "refresh_token": "<string>",
  "expires_in": 123,
  "user": {
    "id": 123,
    "created_at": "2023-11-07T05:31:56Z",
    "telegram_id": 123,
    "username": "<string>",
    "first_name": "<string>",
    "last_name": "<string>",
    "email": "<string>",
    "email_verified": false,
    "balance_kopeks": 0,
    "balance_rubles": 0,
    "referral_code": "<string>",
    "language": "ru",
    "auth_type": "telegram"
  },
  "token_type": "bearer",
  "campaign_bonus": {
    "campaign_name": "<string>",
    "bonus_type": "<string>",
    "balance_kopeks": 0,
    "subscription_days": 123,
    "tariff_name": "<string>"
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.bedolagam.ru/llms.txt

Use this file to discover all available pages before exploring further.

Body

application/json

Request for Telegram WebApp initData authentication.

​
init_data
string
required

Telegram WebApp initData string

Maximum string length: 4096
​
campaign_slug
string | null

Campaign slug from web link

Required string length: 1 - 64
Pattern: ^[a-zA-Z0-9_-]+$
​
referral_code
string | null

Referral code of inviter

Maximum string length: 32
Pattern: ^[a-zA-Z0-9_-]+$

Response

Successful Response

Full authentication response with tokens and user.

​
access_token
string
required
​
refresh_token
string
required
​
expires_in
integer
required
​
user
UserResponse · object
required

User data response.

​
token_type
string
default:bearer
​
campaign_bonus
CampaignBonusInfo · object

Info about campaign bonus applied during auth.