TON Connect SDK

Use it to connect your app to TON wallets via TonConnect protocol.
You can find more details and the protocol specification in the docs.
See the example of sdk usage here.

Latest API documentation

Getting started

Installation with cdn

Add the script to your HTML file:
``html

`

ℹ️ If you don't want auto-update the library, pass concrete version instead of latest, e.g.
`html

`

You can find TonConnect in global variable TonConnectSDK, e.g.
`html

`

Installation with npm


npm i @tonconnect/sdk

Usage

Init connector and call restoreConnection. If user connected his wallet before, connector will restore the connection

`ts
import TonConnect from '@tonconnect/sdk';

const connector = new TonConnect();

connector.restoreConnection();
`

Add the tonconnect-manifest


App needs to have its manifest to pass meta information to the wallet. Manifest is a JSON file named as tonconnect-manifest.json following format:

`json
{
"url": "", // required
"name": "", // required
"iconUrl": "", // required
"termsOfUseUrl": "", // optional
"privacyPolicyUrl": "" // optional
}
`

Best practice is to place the manifest in the root of your app, e.g. https://myapp.com/tonconnect-manifest.json. It allows the wallet to handle your app better and improve the UX connected to your app.
Make sure that manifest is available to GET by its URL.

See details

If your manifest placed not in the root of your app, you can specify its path:
`ts
const connector = new TonConnect({
manifestUrl: 'https://myApp.com/assets/tonconnect-manifest.json'
});
`

Analytics

You can configure analytics collection when creating the connector:

`ts
const connector = new TonConnect({
manifestUrl: 'https://myApp.com/tonconnect-manifest.json',
analytics: { mode: 'off' } // or 'telemetry' (default), 'full'
});
`

Analytics modes:

| Mode | Description |
|-------------------------|------------------------------------------------------------|
| off | Analytics turned off. No events are collected or sent. |
| telemetry (default) | Analytics used for technical research and issue debugging. |
| full | Full analytics events. |

Subscribe to the connection status changes


`js
const unsubscribe = connector.onStatusChange(
walletInfo => {
// update state/reactive variables to show updates in the ui
}
);

// call unsubscribe() later to save resources when you don't need to listen for updates anymore.
`

Fetch wallets list

TonConnect is build to support different wallets. You can fetch all supported wallets list and show a custom wallet selection dialog for user.

`ts
const walletsList = await connector.getWallets();

/* walletsList is
{
name: string;
imageUrl: string;
tondns?: string;
aboutUrl: string;
universalLink?: string;
deepLink?: string;
bridgeUrl?: string;
jsBridgeKey?: string;
injected?: boolean; // true if this wallet is injected to the webpage
embedded?: boolean; // true if the dapp is opened inside this wallet's browser
}[]
*/
`

You also can get wallets list using getWallets static method:
`ts
const walletsList = await TonConnect.getWallets();
`

$3

Following type guards might be helpful for WalletInfos manipulations:

`ts
import {
isWalletInfoCurrentlyEmbedded,
isWalletInfoInjectable,
isWalletInfoCurrentlyInjected,
isWalletInfoRemote,
WalletInfo
} from '@tonconnect/sdk';

/ Use for filtration /
const remoteConnectionWalletInfos = walletInfoList.filter(isWalletInfoRemote);

// all wallets that supports injecteble connection (EVEN THOSE THAT ARE NOT INJECTED TO THE CURRENT PAGE)
const injectableConnectionWalletInfos = walletInfoList.filter(isWalletInfoInjectable);

// wallets that are injected to the current webpage
const currentlyInjectedWalletInfos = walletInfoList.filter(isWalletInfoCurrentlyInjected);
const embeddedWalletInfo = walletInfoList.find(isWalletInfoCurrentlyEmbedded);


/ or use as type guard /
if (isWalletInfoRemote(walletInfo)) {
connector.connect({
universalLink: walletInfo.universalLink,
bridgeUrl: walletInfo.bridgeUrl
});
return;
}

if (isWalletInfoCurrentlyInjected(walletInfo)) {
connector.connect({
jsBridgeKey: walletInfo.jsBridgeKey
});
return;
}
`

Initialize a wallet connection when user clicks to 'connect' button in your app

$3

`ts
// Should correspond to the wallet that user selects
const walletConnectionSource = {
universalLink: 'https://app.tonkeeper.com/ton-connect',
bridgeUrl: 'https://bridge.tonapi.io/bridge'
}

const universalLink = connector.connect(walletConnectionSource);
`

Then you have to show this link to user as QR code, or use it as a deeplink. You will receive an update in connector.onStatusChange when user approves connection in the wallet.

$3


`ts
// Should correspond to the wallet that user selects
const walletConnectionSource = {
jsBridgeKey: 'tonkeeper'
}

connector.connect(walletConnectionSource);
`

You will receive an update in connector.onStatusChange when user approves connection in the wallet.

$3

You can create the unified link that could be accepted by any wallet. To do that you should pass an array of http-wallet-connection-sources:

If several wallets have same bridge url, you can pass this url only once.
`ts
const sources = [
{
bridgeUrl: 'https://bridge.tonapi.io/bridge' // Tonkeeper
},
{
bridgeUrl: 'https://' // Tonkeeper
}
];

connector.connect(sources);
`

$3


It is recommended not to show a QR code modal if the app is opened inside a wallet's browser.
You should detect working environment of the app and show appropriate UI.
Check embedded property in elements of the wallets list to detect if the app is opened inside a wallet.

`ts
import { isWalletInfoCurrentlyEmbedded, WalletInfoCurrentlyEmbedded } from '@tonconnect/sdk';

// "connect button" click handler.
// Execute this before show wallet selection modal.

const walletsList = await connector.getWallets(); // or use walletsList fetched before

const embeddedWallet = walletsList.find(isWalletInfoCurrentlyEmbedded) as WalletInfoCurrentlyEmbedded;

if (embeddedWallet) {
connector.connect({ jsBridgeKey: embeddedWallet.jsBridgeKey });
return;
}

// else show modal and ask user to select a wallet
`

Send transaction


`ts
if (!connector.connected) {
alert('Please connect wallet to send the transaction!');
}

const transaction = {
validUntil: Math.floor(Date.now() / 1000) + 60, // 60 sec
messages: [
{
address: "EQBBJBB3HagsujBqVfqeDUPJ0kXjgTPLWPFFffuNXNiJL0aA",
amount: "20000000",
// stateInit: "base64bocblahblahblah==" // just for instance. Replace with your transaction initState or remove
},
{
address: "EQDmnxDMhId6v1Ofg_h5KR5coWlFG6e86Ro3pc7Tq4CA0-Jn",
amount: "60000000",
// payload: "base64bocblahblahblah==" // just for instance. Replace with your transaction payload or remove
}
]
}

try {
const result = await connector.sendTransaction(transaction);

// you can use signed boc to find the transaction
const someTxData = await myAppExplorerService.getTransaction(result.boc);
alert('Transaction was sent successfully', someTxData);
} catch (e) {
if (e instanceof UserRejectedError) {
alert('You rejected the transaction. Please confirm it to send to the blockchain');
} else {
alert('Unknown error happened', e);
}
}
`

You can pass a custom trace ID to track the transaction through your analytics:

`ts
const result = await connector.sendTransaction(transaction, {
traceId: '019a2a92-a884-7cfc-b1bc-caab18644b6f' // optional, UUIDv7 auto-generated if not provided
});

console.log(result.traceId); // use this ID to correlate with analytics events
`

Sign data

Sign arbitrary data with the user's wallet. The wallet will display the data to the user for confirmation before signing.

$3

You can sign three types of data. Choose the right format based on your use case:

- Text - Use for human-readable text that users should see and understand
- Cell - Use for TON Blockchain data that should be used in smart contracts (wallet may show unknown content warning)
- Binary - For other arbitrary data (least preferred due to security warnings)

#### Text Format

Use when you need to sign human-readable text. The wallet displays the text to the user.

Parameters:
- type (string, required): Must be "text"
- text (string, required): UTF-8 text to sign
- network (string, optional): "-239" for mainnet, "-3" for testnet
- from (string, optional): Signer address in raw format "0:"

`ts
const textData = {
type: "text",
text: "Confirm new 2fa number:\n+1 234 567 8901",
network: "-239", // MAINNET = '-239', TESTNET = '-3'
from: "0:348bcf827469c5fc38541c77fdd91d4e347eac200f6f2d9fd62dc08885f0415f"
};

try {
const result = await connector.signData(textData);
console.log('Signed:', result);
} catch (e) {
if (e instanceof UserRejectedError) {
console.log('User rejected signing');
} else {
console.error('Error:', e);
}
}
`

You can also pass a trace ID to correlate with analytics:

`ts
const result = await connector.signData(textData, {
traceId: '019a2a92-a884-7cfc-b1bc-caab18644b6f' // optional, UUIDv7 auto-generated if not provided
});

console.log(result.traceId); // use this ID to correlate with analytics events
`

#### Binary Format

Use for arbitrary binary data. The wallet shows a warning about unknown content.

Parameters:
- type (string, required): Must be "binary"
- bytes (string, required): Base64 encoded binary data (not url-safe)
- network (string, optional): "-239" for mainnet, "-3" for testnet
- from (string, optional): Signer address in raw format "0:"

`ts
const binaryData = {
type: "binary",
bytes: "1Z/SGh+3HFMKlVHSkN91DpcCzT4C5jzHT3sA/24C5A==",
network: "-239", // MAINNET = '-239', TESTNET = '-3'
from: "0:348bcf827469c5fc38541c77fdd91d4e347eac200f6f2d9fd62dc08885f0415f"
};

try {
const result = await connector.signData(binaryData);
console.log('Signed:', result);
} catch (e) {
if (e instanceof UserRejectedError) {
console.log('User rejected signing');
} else {
console.error('Error:', e);
}
}
`

#### Cell Format

Use for TON Blockchain data with TL-B schema. The wallet can parse and display the content if the schema is valid.

Parameters:
- type (string, required): Must be "cell"
- schema (string, required): TL-B schema of the cell payload
- cell (string, required): Base64 encoded BoC (not url-safe) with single-root cell
- network (string, optional): "-239" for mainnet, "-3" for testnet
- from (string, optional): Signer address in raw format "0:"

`ts
const cellData = {
type: "cell",
schema: "transfer#0f8a7ea5 query_id:uint64 amount:(VarUInteger 16) destination:MsgAddress response_destination:MsgAddress custom_payload:(Maybe ^Cell) forward_ton_amount:(VarUInteger 16) forward_payload:(Either Cell ^Cell) = InternalMsgBody;",
cell: "te6ccgEBAQEAVwAAqg+KfqVUbeTvKqB4h0AcnDgIAZucsOi6TLrfP6FcuPKEeTI6oB3fF/NBjyqtdov/KtutACCLqvfmyV9kH+Pyo5lcsrJzJDzjBJK6fd+ZnbFQe4+XggI=",
network: "-239", // MAINNET = '-239', TESTNET = '-3'
from: "0:348bcf827469c5fc38541c77fdd91d4e347eac200f6f2d9fd62dc08885f0415f"
};

try {
const result = await connector.signData(cellData);
console.log('Signed:', result);
} catch (e) {
if (e instanceof UserRejectedError) {
console.log('User rejected signing');
} else {
console.error('Error:', e);
}
}
`

$3

All signData calls return the same response structure:

`ts
interface SignDataResult {
signature: string; // Base64 encoded signature
address: string; // Wallet address in raw format
timestamp: number; // UNIX timestamp in seconds (UTC)
domain: string; // App domain name
payload: object; // Original payload from the request
}
`

$3

After receiving the signed data, you need to verify the signature to ensure it's authentic and was signed by the claimed wallet address.

For backend verification: See TypeScript verification example showing how to verify signatures on your server.

For smart contract verification: See FunC verification example showing how to verify signatures in TON smart contracts.

For complete technical details: See the Sign Data specification for full signature verification requirements.

Disconnect wallet


Note that if you want to change connected wallet, you should disconnect current one firstly. Also make sure that you've waited for restoreConnection() promise resolved before call disconnect();

`ts
if (connector.connected) {
await connector.disconnect();
}
`


Utils

Convert address to user-friendly format


Use toUserFriendlyAddress function to convert raw-address to the user-friendly format. You can pass true as a second
parameter to make it 'testnet only' (disabled by default).


`ts
import { toUserFriendlyAddress } from '@tonconnect/sdk';

const rawAddress = connector.wallet.account.address; // like '0:abcdef123456789...'
const bouncableUserFriendlyAddress = toUserFriendlyAddress(rawAddress);
const testnetOnlyBouncableUserFriendlyAddress = toUserFriendlyAddress(rawAddress, true);
`

Backend authorization


To authorize user in your backend with TonConnect you can use following schema:
1. Fetch auth payload from your backend. It might be any random value. Backend must save information that this payload was sent to the client to check payload correctness later.
2. Connect to the wallet when user clicks to the connection button:
`ts
connector.connect(
walletConnectionSource,
{ tonProof: "" }
);
`
Note that you can use tonProof only with connector.connect() method. This feature is not available in connector.restoreConnection().

$3

You can specify the desired network before connecting to a wallet using the setConnectionNetwork() method. If the wallet connects to a different network, the connection will be aborted with a WalletWrongNetworkError.

`ts
import { CHAIN, WalletWrongNetworkError } from '@tonconnect/sdk';

const connector = new TonConnect();

// Set desired network before connecting, possible values is CHAIN.MAINNET ('-239'), CHAIN.TESTNET ('-3'), or any custom chainId string
connector.setConnectionNetwork(CHAIN.MAINNET);

// Or allow any network if needed (default behavior)
// connector.setConnectionNetwork(undefined);

// And connect wallet
connector.connect(walletConnectionSource);

// Handle network mismatch error
connector.onStatusChange(
wallet => { / ... / },
error => {
if (error instanceof WalletWrongNetworkError) {
console.error('Wrong network:', error.cause.expectedChainId, 'vs', error.cause.actualChainId);
// UI will display a user-friendly error message
}
}
);
`

Important:
- Network must be set before calling connect(). Attempting to change network while connected will throw an error.
- Network validation is also performed for sendTransaction and signData operations if a network was specified.

3. Read a signed result after user approves connection:
`ts
connector.onStatusChange(wallet => {
if (!wallet) {
return;
}

const tonProof = wallet.connectItems?.tonProof;

if (tonProof) {
if ('proof' in tonProof) {
// send proof to your backend
// e.g. myBackendCheckProof(tonProof.proof, wallet.account);
return;
}

console.error(tonProof.error);
}
});
`
4. Send proof and user's account data to your backend. Backend should check the proof correctness and check that payload inside the proof was generated before. After all checks backend should return an auth token to the client. Notice that Account contains the walletStateInit property which can be helpful for your backend to get user's public key if user's wallet contract doesn't support corresponding get method.
5. Client saves the auth token in the localStorage and use it to access to auth-required endpoints. Client should delete the token when user disconnects the wallet.

See an example of a dapp using backend authorization.

See an example of the dapp backend.




Use with NodeJS

You can use the SDK in frontend apps and in backend apps created with NodeJS.

Installation

npm i @tonconnect/sdk

Init connector

When you use the SDK in backend, you have to pass manifestUrl and IStorage implementation to the TonConnect constructor.

See more about the manifest.

`ts
import TonConnect from '@tonconnect/sdk';

const storage: IStorage =

const connector = new TonConnect({ manifestUrl, storage });
`

Your storage should implement following interface:
`ts
export interface IStorage {
setItem(key: string, value: string): Promise;
getItem(key: string): Promise;
removeItem(key: string): Promise;
}
`

See details about IStorage in the API documentation.

Other steps are the same as for browser apps.

Pause and unpause connection


You can pause and unpause HTTP connection using tonConnect.pauseConnection() and tonConnect.unPauseConnection() to save your server resources.

`ts
myTelegramBot.userIsOffline(user => {
const connector = myFunctionGetConnectorByUser(user);
connector.pauseConnection();
})

myTelegramBot.userIsOnline(user => {
const connector = myFunctionGetConnectorByUser(user);
connector.unPauseConnection();
})
`

Tracking

Track events

Tracker for TonConnect user actions, such as transaction signing, connection, etc.

List of events:
* connection-started: when a user starts connecting a wallet.
* connection-completed: when a user successfully connected a wallet.
* connection-error: when a user cancels a connection or there is an error during the connection process.
* connection-restoring-started: when the dApp starts restoring a connection.
* connection-restoring-completed: when the dApp successfully restores a connection.
* connection-restoring-error: when the dApp fails to restore a connection.
* disconnection: when a user starts disconnecting a wallet.
* transaction-sent-for-signature: when a user sends a transaction for signature.
* transaction-signed: when a user successfully signs a transaction.
* transaction-signing-failed: when a user cancels transaction signing or there is an error during the signing process.
* sign-data-request-initiated: when a user initiates a request to sign data.
* sign-data-request-completed: when a user successfully signs data.
* sign-data-request-failed: when a user cancels data signing or there is an error during the signing process.

If you want to track user actions, you can subscribe to the window events with prefix ton-connect-:

`typescript
window.addEventListener('ton-connect-transaction-sent-for-signature', (event) => {
console.log('Transaction init', event.detail);
});
`

Use custom event dispatcher

You can use your custom event dispatcher to track user actions. To do this, you need to pass the eventDispatcher to the TonConnect constructor:

`typescript
import {TonConnect, EventDispatcher, SdkActionEvent} from '@tonconnect/sdk';

class CustomEventDispatcher implements EventDispatcher {
public async dispatchEvent(
eventName: string,
eventDetails: SdkActionEvent
): Promise {
console.log(Event: ${eventName}, details:, eventDetails);
}
}

const eventDispatcher = new CustomEventDispatcher();

const connector = new TonConnect({ eventDispatcher });
`




Troubleshooting

Warning about 'encoding' module in Next.js

If you are using Next.js and see a warning similar to the following:

`
⚠ ./node_modules/node-fetch/lib/index.js
Module not found: Can't resolve 'encoding' in '.../node_modules/node-fetch/lib'

Import trace for requested module:
./node_modules/node-fetch/lib/index.js
./node_modules/@tonconnect/isomorphic-fetch/index.mjs
./node_modules/@tonconnect/sdk/lib/esm/index.mjs
`

Please note that this is just a warning and should not affect the functionality of your application. If you wish to suppress the warning, you have two options:

1. (Recommended) Wait for us to remove the dependency on @tonconnect/isomorphic-fetch in future releases. This dependency will be removed when we drop support for Node.js versions below 18.

2. (Optional) Install the encoding package, to resolve the warning:
`shell
npm install encoding
``