TypeScript Setup
Learn how to create a TypeScript application and initialize it with the Okto SDK, including setting up authentication and executing your first token transfer.
Quick Start Template Available!
Skip the manual setup and get started in minutes with our template repository. Please note that this template is for development and testing purposes only. Be sure to customize and secure it before using in production.
TypeScript App
This approach shows how to create a TypeScript application and manually configure the Okto SDK. Follow these steps to set up your project and execute your first token transfer.
Prerequisites
Before you begin, set up your developer dashboard by making sure you have :
- Created your Okto Developer Dashboard account
- Get your Okto credits from the dashboard
- Obtained your API keys from the dashboard
- Enabled the specific Chains and Tokens you plan to use in your application
- Optional: Enabled Sponsorship for the desired chains
If you need help, reach out to us on our troubleshooting form and we will contact you.
Before getting started, ensure you have the following:
- Node.js (v18+) and npm/pnpm/yarn: Download Node.js
- Okto API Keys: You need your
CLIENT_PRIVATE_KEY
andCLIENT_SWA
. Obtain these from the Okto Developer Dashboard. - Okto Account Setup: Ensure you have sufficient Okto Credits, enable the required Chains and Tokens , and optionally Activate Sponsorship.
- Google OAuth Credentials (if using Google authentication): Create OAuth 2.0 credentials in the Google Cloud Console to get your
GOOGLE_CLIENT_ID
.
- Go to Google Cloud Console.
- Create OAuth 2.0 credentials for your project.
- Set the redirect URI to:
[YOUR_APP_URL]/api/auth/callback/google
(for example,http://localhost:3000/api/auth/callback/google
during local development). - Save your Client ID.
Need detailed instructions? Check our Google Console Setup Guide.
Sponsorship Setup (Optional)
To enable sponsorship for transactions via Okto, follow the steps below:
-
Enable Supported Chains: Ensure the chains you wish to sponsor transactions on are enabled in your Okto Dashboard under Chains & Tokens.
-
Create and Configure a Treasury Wallet: Create at least one Treasury Wallet in your Okto Dashboard.
- For each supported chain:
- The Treasury Wallet used as the
feePayerAddress
must have its corresponding destination chain address funded with a small amount of native tokens for one-time verification. - Refer to the Treasury Wallet Docs for setup and verification details.
- The Treasury Wallet used as the
-
Activate Sponsorship: Navigate to the Sponsorship section in the Okto Dashboard and enable sponsorship for each chain individually.
-
Fund the Sponsor Wallet: Deposit a sufficient amount of native tokens into your Sponsor Wallet for each chain where sponsorship is active. These tokens will be used to cover user transaction fees.
- Only native tokens of the respective chains can be loaded into sponsorship accounts.
- Each chain has a unique sponsorship address. You can find this address in your Okto dashboard.
- For testnets, you can use faucets to acquire tokens.
Initialize a TypeScript Project
If you already have a TypeScript project, you can skip this step and proceed directly to Step 2 to start integrating Okto.
mkdir my-okto-app
cd my-okto-app
npm init -y
npm install typescript @types/node --save-dev
npx tsc --init
Install Dependencies
Install the required packages:
npm install @okto_web3/core-js-sdk@latest
pnpm add @okto_web3/core-js-sdk@latest
yarn add @okto_web3/core-js-sdk@latest
Configure Environment Variables
Create a .env
file in your project root:
CLIENT_PRIVATE_KEY=YOUR_CLIENT_PRIVATE_KEY
CLIENT_SWA=YOUR_CLIENT_SWA
ENVIRONMENT=sandbox
Create a configuration file to load these variables:
import * as dotenv from 'dotenv';
dotenv.config();
export const config = {
environment: process.env.ENVIRONMENT || 'sandbox',
clientPrivateKey: process.env.CLIENT_PRIVATE_KEY! ,
clientSWA: process.env.CLIENT_SWA!,
};
Initialize Okto Client
Create your main file:
import { Hash, Hex, OktoClient } from '@okto_web3/core-js-sdk';
import { config } from './config';
const oktoClient = new OktoClient({
environment: config.environment,
clientPrivateKey: config.clientPrivateKey as Hash,
clientSWA: config.clientSWA as Hex,
});
async function main() {
// Your code will go here
console.log("Okto client initialized!");
}
main().catch(console.error);
Implement Authentication
Currently, you can onboard users and support on-chain interaction via the Okto Embedded wallet. To do this you must first authenticate your user via social login. We currently support Google OAuth.
Update your main file to include authentication:
async function authenticate(idToken: string) {
try {
const user = await oktoClient.loginUsingOAuth({
idToken,
provider: "google",
});
console.log("Authentication successful:", user);
return user;
} catch (error) {
console.error("Authentication failed:", error);
throw error;
}
}
Congratulations!
🎉 Your basic Okto integration is now complete! You're ready to bring your dApp to life. Let's try out a simple user operation!
Trying Out a User Operation
Now that we have our basic setup complete, let's implement a token transfer on Polygon Amoy Testnet to understand how user operations work in Okto.
1. Get Your Wallet Address
First, get your Polygon wallet address:
import { getAccount } from "@okto_web3/react-sdk";
const accounts = await getAccount(oktoClient);
const polygonAccount = accounts.data.find(account => account.network_name === "POLYGON_TESTNET_AMOY");
console.log("Your Polygon Amoy address:", polygonAccount.address);
2. Fund Your Wallet
To perform a token transfer, you'll need some funds in your wallet. Add funds to this address using the Polygon Amoy Faucet.
3. Check Network Information
Before creating the user operation, check the Network Information Guide for getting the correct CAIP-2 IDs of chains.
4. Implement Token Transfer
Add this function to your main file:
import { tokenTransfer } from "@okto_web3/core-js-sdk";
async function handleTransfer() {
try {
const transferParams = {
amount: BigInt("1000000000000000000"), // 1 POL (18 decimals)
recipient: "RECIPIENT_ADDRESS",
token: "", // Empty string for native token
caip2Id: "eip155:80002" // Polygon Amoy Testnet chain ID
};
// Execute the transfer
const jobId = await tokenTransfer(oktoClient, transferParams);
console.log(`Transfer jobId! Result: ${jobId}`);
} catch (error) {
console.error("Transfer failed:", error);
throw error;
}
}
Verify The Transfer
After the transfer is complete, you can verify it through:
- The
getPortfolio
method to check your updated balance - The Polygon Amoy Explorer using the transaction hash which can be fetched using the
getOrdersHistory
method using thejobId
.
Now that you've completed your first user operation, you're ready to explore more advanced features! Check out our Usage Guide to learn about other operations like NFT transfers, contract interactions, and more.
SDK Reference
Get Commands
Method | Description | Documentation |
---|---|---|
const account = await getAccount(oktoClient); | Get user's wallet details | Method Overview |
const chains = await getChains(oktoClient); | List supported blockchain networks | Method Overview |
const tokens = await getTokens(oktoClient); | List supported tokens | Method Overview |
const portfolio = await getPortfolio(oktoClient); | Get user's token holdings | Method Overview |
const nfts = await getPortfolioNFT(oktoClient); | Get user's NFT holdings | Method Overview |
const activity = await getPortfolioActivity(oktoClient); | Get transaction history | Method Overview |
const orders = await getOrdersHistory(oktoClient); | Get transaction order history | Method Overview |
const collections = await getNftCollections(oktoClient); | Get NFT collections | Method Overview |
Message Signing
Enables the creation of signatures for messages or object data. The signing process is initiated through the OktoClient instance.
Command | Description | Documentation |
---|---|---|
const signature = await oktoClient.signMessage(message); | Signs messages following the EIP191 standard | Method Overview |
const signature = await oktoClient.signTypedData(data); | Signs typed data following the EIP712 standard | Method Overview |
User Operations (Intents)
Intents are pre-built action templates within the Okto SDK that simplify common Web3 tasks. They provide one-liner functions for complex blockchain interactions.
1. Token Transfer
Send tokens to another address. Learn more
const transferParams = {
amount: BigInt("1000000000000000000"), // Amount in smallest unit
recipient: "0xRecipientAddress...", // Recipient wallet address
token: "0xTokenAddress...", // Token address ("" for native token)
caip2Id: "eip155:1", // Target chain CAIP-2 ID
};
const result = await tokenTransfer(oktoClient, transferParams);
2. NFT Transfer
Transfer NFTs between addresses. Learn more
const nftParams = {
caip2Id: "eip155:1", // Target chain CAIP-2 ID
collectionAddress: "0xCollectionAddress...", // NFT Collection address
nftId: "NFTTokenID", // NFT identifier
recipientWalletAddress: "0xRecipientAddress...",// Recipient address
amount: 1n,
nftType: "ERC721", // or "ERC1155"
};
const result = await nftTransfer(oktoClient, nftParams);
3. Raw Transaction (EVM)
Execute custom EVM contract calls. Learn more
import { encodeFunctionData } from 'viem';
// 1. Define Contract Interaction
const contractAddress = '0xContractAddress...';
const functionName = 'setValue';
const functionArgs = [123];
// 2. Encode Function Data
const functionData = encodeFunctionData({
abi: [
{
"name": functionName,
"type": "function",
"stateMutability": "nonpayable",
"inputs": [{ "type": "uint256", "name": "_value" }]
}
] as const,
functionName,
args: functionArgs,
});
// 3. Execute Transaction
const rawTxParams = {
caip2Id: "eip155:1",
transaction: {
to: contractAddress,
data: functionData,
// value: BigInt(0), // Optional: for payable functions
},
};
const result = await evmRawTransaction(oktoClient, rawTxParams);
Quick Start Template Available!
Skip the manual setup and get started in minutes with our template repository. Please note that this template is for development and testing purposes only. Be sure to customize and secure it before using in production.
Additional Resources
Need help? Join our Discord community or email us at [email protected]
.