Overview of Okto SDKs

Okto provides a suite of SDKs tailored to different platforms, enabling you to integrate Web3 functionalities effortlessly. Whether you're building for the web, mobile, or other platforms, Okto has an SDK to match your needs. Below is an overview of each SDK, its use case, and links to get started.

1. React SDK

The React SDK is designed for developers building Web3 applications for the web. It simplifies blockchain interactions, enabling seamless onboarding and smooth user experiences.

Use Case: Web applications


2. React Native SDK

If you’re developing mobile-first Web3 applications, the React Native SDK is your go-to option. It provides all the tools necessary to onboard users to Web3 seamlessly.

Use Case: Mobile applications for iOS and Android


3. Flutter SDK

The Flutter SDK caters to developers using Flutter and Dart to build cross-platform mobile applications. It reduces setup complexity and enhances user experiences.

Use Case: Cross-platform mobile applications (Android and iOS)


4. Unity SDK

The Unity SDK will empower game developers to integrate Web3 features into their games across platforms such as web, mobile, and desktop.

Use Case: Web3-enabled gaming experiences


5. API Integration

For projects that don’t rely on specific frameworks, the Okto API provides a direct way to integrate Web3 functionalities. Use it to build custom solutions for your unique needs.

Use Case: Server-side or client-side Web3 applications without framework dependencies


Get Started Today

Pick your SDK and start building.

Okto SDKs are designed to make Web3 development as seamless as possible. Dive into the detailed guides for each SDK and bring your applications to life with blockchain-powered features.


Important Implementation Note

When working with Okto's APIs and SDKs, please note that the order of elements in responses is not guaranteed to remain consistent between different calls. Always write code that explicitly checks for specific properties rather than relying on the position of elements in the response.

Example

Let's say you're fetching a user's wallets:

// First API call might return:
{
  "wallets": [
    {
      "network_name": "APTOS",
      "address": "0x8d4e7a9cef2b53e35e0273e3ef4eccf114ae95ca7a75da79c6cbd416f9b12ab3",
      "success": true
    },
    {
      "network_name": "POLYGON",
      "address": "0x156ba3f2d578B9Cd233f8D3fd07b7f78dC2D4921",
      "success": true
    },
    {
      "network_name": "SOLANA_DEVNET",
      "address": "7KPHCFnLfh7KSqKVZwGr8dgTqwiAZBpLvmknhmmtXBCd",
      "success": true
    }
  ]
}
 
// A subsequent call might return the same data in a different order:
{
  "wallets": [
    {
      "network_name": "POLYGON",
      "address": "0x156ba3f2d578B9Cd233f8D3fd07b7f78dC2D4921",
      "success": true
    },
    {
      "network_name": "SOLANA_DEVNET",
      "address": "7KPHCFnLfh7KSqKVZwGr8dgTqwiAZBpLvmknhmmtXBCd",
      "success": true
    },
    {
      "network_name": "APTOS",
      "address": "0x8d4e7a9cef2b53e35e0273e3ef4eccf114ae95ca7a75da79c6cbd416f9b12ab3",
      "success": true
    }
  ]
}

Incorrect Usage - Don't rely on array positions:

const polygonWallet = response.wallets[0].address;  // Assumes Polygon wallet is first

Correct Usage - Find the wallet you need by its network name:

const polygonWallet = response.wallets.find(wallet => wallet.network_name === 'POLYGON')?.address;

This principle applies to all list-type responses from Okto's APIs and SDKs. Always write code that explicitly looks for the data you need rather than assuming a specific order.

On this page