auth
Auth via telegram
Changed onThe token is recorded in the database and in the user's cookies. If the user logs in under different browsers, then each authorization will have its own token.
post/api/v1/auth/tg
Request
- Base URLhttp://localhost:8888
- Authnone declared
Request body
Example request
{
"id": 1261871881,
"first_name": "Test",
"last_name": "Test",
"photo_url": "https://test_image.png",
"username": "test",
"hash": "cd0e201bf7328535343301f428e51f01084a3e2a3822f4843d86b540bbebfe15",
"auth_date": 1678275313,
"referral_id": "ref_test"
}Response
Ok
Example response
{
"ok": true
}Changes
- info
added the new optional request property
- info
- info
api operation id
authViaTGwas added
- info