> ## Documentation Index
> Fetch the complete documentation index at: https://veriqa.app/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Telegram

> Step-by-step screens for the Telegram channel: signing in on a computer and on a phone, step-up, collecting extra details, and the claims your app can get.

## General scheme

A sign-in starts in your app: it sends the browser to the sign-in page with a standard OpenID Connect redirect. The user
confirms in a channel, and the browser returns to your app with a code that your app exchanges for tokens.

![Signing in through Veriqa: your app sends the browser to the sign-in page by an OpenID Connect redirect, the person confirms in a channel, and Veriqa redirects back so your app can exchange the code for tokens.](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-flow-sign-in.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=ded6eede4a7e26ade7410dd12eb871de)

An action confirmation starts on your server: it creates a transaction through the Veriqa API. The user confirms in a
channel, and your server reads the answer and performs the action. The browser is not redirected.

![Confirming an action through Veriqa: your server creates the transaction, the person scans the QR code your app shows and confirms in a channel, and your server reads the answer and performs the action.](https://mintcdn.com/veriqa/XLg27VdhWjZL50TY/images/examples/en-flow-confirm.webp?fit=max\&auto=format\&n=XLg27VdhWjZL50TY\&q=85\&s=03bda77eac10a8b5d7423cfc53fc142b)

See [Basic scenarios](https://veriqa.app/docs/basic-scenarios.md).

## Signing in on a computer

![Signing in on a computer with Telegram: the sign-in window shows a QR code, the phone camera scans it, the user taps Confirm in the Telegram chat, and the chat replies "Sign-in confirmed".](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-telegram-cross-device.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=83822cdb7c6dea4c6378491adb285665)

The user scans the QR code with their phone camera and confirms in the Telegram chat.

## Signing in on a phone

![Signing in on a phone: the user taps "Sign in with Telegram", confirms in the Telegram chat, and the chat replies "Sign-in confirmed".](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-telegram-phone.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=c4f0468d1de8643cfb50643c8cb0b2e1)

The user taps "Sign in with Telegram" and confirms in the Telegram chat.

## Step-up: confirming an action

![Confirming an action: the app shows a QR code for deleting a project, the phone camera scans it, the user gets the request in Telegram, and the decision goes back to the app.](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-telegram-confirm.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=ab6865aea1dbbd877c9ab587cce1b6ef)

The app shows a QR code, and the user scans it with their phone camera and declines the request in Telegram. The app receives the answer.

## Collecting extra details at sign-in

![Collecting extra details at sign-in: after confirming in Telegram, the user shares a phone number, fills in the missing fields of a short form, confirms the email with one ready-made message, and the app receives the verified claims.](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-telegram-progressive.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=73b3a64321c0161e6c60de18bbece412)

At sign-in, your app gets what the messaging app doesn't provide: a phone number, answers to a short form and a confirmed email address.

The last frame of the animation shows test values from a real ID token.

## Claims your app can get

![Claims your app can get from signing in with Telegram: sub, amr, channel\_type, channel\_user\_id, name, given\_name, family\_name, preferred\_username, locale, picture, phone\_number, phone\_number\_verified true, and email with email\_verified after an email confirmation.](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-telegram-claims.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=1990d6f4ae645a60d5bb69712bdc80d8)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.