---
title: "Auth via TON Connect"
method: POST
path: "/api/v1/auth/proof/check"
tags: ["auth"]
---

# Auth via TON Connect

`POST /api/v1/auth/proof/check`

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.

## Request body

- TonConnectProof
  - `promo_code` string
  - `address` string, required
  - `proof` object, required
    - `timestamp` integer
    - `domain` string
    - `signature` string
    - `payload` string
    - `state_init` string

## Response `200`

Ok

- Ok
  - `ok` boolean, required

## Other responses

- `400` — Something went wrong on client side
- `403` — Access token is missing or invalid
- `404` — The specified resource was not found
- `500` — Something went wrong on server side

---

[API](https://skmtc.net/tonkeeper/apis/rest-api-to-ton-console.md) · [All operations](https://skmtc.net/tonkeeper/apis/rest-api-to-ton-console/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/tonkeeper/rest-api-to-ton-console/versions/bffcc11719d3/schema)