auth

Auth via TON Connect

The 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/proof/check

Request body

promo_codestring

addressstring required

Example request

{
  "address": "0:97146a46acc2654y27947f14c4a4b14273e954f78bc017790b41208b0043200b",
  "proof": {
    "payload": "84jHVNLQmZsAAAAAZB0Zryi2wqVJI-KaKNXOvCijEi46YyYzkaSHyJrMPBMOkVZa"
  }
}

Response

okboolean required

Example response

{
  "ok": true
}

Changes

Changed in 2 of the 50 revisions of this API.2

Oct 21, 2025356252841f501See the full diff
- ○
  added the new optional request property promo_code
  new-optional-request-property
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Jun 14, 20245d8d7caae34c1See the full diff
- ○
  api operation id authViaTonConnect was added
  api-operation-id-added

Full history