SDK & API Framework

Wallets for your
app and backend.

A React Native SDK, a Node.js SDK and a REST API with webhooks, all on one wallet platform. Texavio runs signing and key management on 30+ chains, so there are no key servers for your team to operate.

See how it works
SDKsReact Native · Node.js
REST+ webhooks
$ npm install @texavio/wallet-sdk
One framework

Use the SDK in your app, the Node.js SDK or REST API on your server, or both together. Every entry point reaches the same wallets, policies and modules.

Client side

React Native SDK

Inside your mobile app

Prebuilt wallet screens and headless hooks for iOS and Android.

  • Themeable UI
  • Device key share
  • Passkey and social login
Server side

Node.js SDK

Inside your backend

A typed client for wallets, transactions and policies.

  • Typed requests
  • Webhook verification
  • Idempotent retries
Any language

REST API + webhooks

Over HTTPS

The same actions as plain HTTPS endpoints, with a signed webhook for each event.

  • Documented endpoints
  • Signed webhooks
  • Sandbox keys
Request flow

Each request is checked at the gateway and against your policies before a key share is used. Texavio co-signs, broadcasts and confirms the transaction, then sends a signed webhook to your server.

Your app or backend
React Native SDK, Node.js SDK or REST
Texavio gateway
mTLS, scoped keys, rate limits
Policy engine
Limits and allowlists
MPC signing
2-of-3 threshold signing
30+ chains
Broadcast and confirmed
Webhook
Signed event to your server
Client side · React Native SDK

The React Native SDK adds wallet screens and logic to your app, so users can sign up, hold, send and swap within your product. It holds the device key share; Texavio co-signs.

Choose the SDK when
  • You have, or are building, a mobile app
  • You want prebuilt wallet screens
  • Users should not need a third-party wallet
  • You do not want to run key or signing servers
9:41
YOUR APP
Balance
$4,218.40
Trading
$300.00
Staked
$228.00
Receive
Send
Swap
AssetsSee all
ETH1.204
SOL18.50
USDC950.00
Passkey login
Continue
Using the SDK

Step 01 · Package

Install

Add the package to your React Native project and wrap the app in the provider.

Step 02 · Settings

Configure

Select key models, chains and modules, and apply your theme to every component.

Step 03 · App stores

Ship

Release the app through your usual process. Wallet creation, signing and recovery run on Texavio.

App.tsxExample setup
1import { TexavioProvider, WalletSheet } from "@texavio/wallet-sdk";
2
3export default function App() {
4  return (
5    <TexavioProvider appId="app_live_…" chains={["ethereum", "solana"]}
6      login={["passkey", "email", "social"]} theme={brandTheme}>
7      <Home />
8      <WalletSheet />   // prebuilt send · receive · swap
9    </TexavioProvider>
10  );
11}

Package and prop names are illustrative; the SDK reference has the full API.

In the SDK

Use the prebuilt screens, or use the headless hooks with your own interface. Both call the same wallet core.

Prebuilt, themeable UI

Login, balance, send, receive, swap and portfolio screens. Colours, type and corner radius follow your theme.

Headless hooks

The same wallet actions exposed as hooks, for teams that render their own interface.

Supported key models

Seed phrase, private key import, 2-of-3 MPC, or social, email and passkey login.

30+ chains, one interface

EVM networks, Solana, Bitcoin, Cosmos, Aptos, TON and Sui. The chain is set by one parameter.

Policy checks before signing

Spend limits and allowlists set in the dashboard are applied before a transaction is signed.

Gas sponsorship

ERC-4337 account abstraction with sponsored gas, session keys and batched transactions.

Mobile network handling

Requests are queued on poor connections. The device key share is kept in secure local storage.

Ramps and cards

Fiat on/off ramps (via partners) and prepaid cards (via licensed issuers) can be added to the same app.

Developer · SDKs

Typed SDKs, with a sandbox.

A React Native SDK for your app and a Node.js SDK for your backend.

Both SDKs wrap the same Wallet API. Build and test against the sandbox before switching to live keys.

  • React Native SDK
  • Node.js SDK
  • Sandbox environment
  • Live and test keys
React NativeNode.js
1npm install @texavio/wallet-sdk
2<TexavioProvider appId=… />
3useWallet().create()
4useWallet().send(0.1, "ETH")
SDK
Installing…
Server side · Node.js SDK and REST API

Your backend creates wallets, sends, swaps and applies policies through the Node.js SDK or plain HTTPS. Webhooks keep your records in sync, and a front end is optional.

Choose the server side when
  • Wallet actions start on your server, not in an app
  • You run exchanges, payouts, treasury or automated flows
  • You need your own logic around each transaction
  • Your stack isn’t React Native, or has no UI at all
POST/v1/wallets
requestyour server
1curl https://api.texavio.com/v1/wallets \
2  -H "Authorization: Bearer $TEXAVIO_KEY" \
3  -d '{ "userId": "usr_8231", "keyModel": "mpc",
4        "chains": ["ethereum", "solana"] }'
200 OK · 184 ms
responsetexavio
1{
2  "id": "wal_3f9a…",
3  "status": "active",
4  "addresses": {
5    "ethereum": "0x7a1c…e93b",
6    "solana": "9xQe…Lm2k"
7  }
8}

Endpoints, packages and fields shown are illustrative; the API reference has the full schema.

Developer · REST API

REST and signed webhooks.

A documented REST API with a webhook for every event.

Backends in any language can create wallets, move funds and handle events. Responses are typed and requests are idempotent.

  • REST + webhooks
  • Idempotent requests
  • Typed responses
  • Any backend language
const wallet = await texavio
.wallets.create({ chain: "ethereum" });
// → wal_3f9a… · 0x7a1c…e93b
Webhooks to your server
wallet.created200 OK
transaction.pending200 OK
policy.passed200 OK
transaction.confirmed200 OK
SDKs
REST · React Native · Node.js
The endpoints

Request and response shapes are the same on every chain. Switching networks changes one field.

Wallets

  • POST/v1/wallets
    Create a wallet for a user
  • GET/v1/wallets/{id}
    Addresses, balances, status
  • POST/v1/wallets/{id}/recover
    Start key recovery

Transactions

  • POST/v1/wallets/{id}/transactions
    Build, check and sign
  • GET/v1/transactions/{id}
    Track to confirmation
  • POST/v1/swaps/quote
    Aggregated swap quote

Policies

  • PUT/v1/policies/{id}
    Limits, allowlists, rules
  • GET/v1/audit-log
    Policy decision history

Webhooks

  • POST/v1/webhooks
    Subscribe to events
  • DELETE/v1/webhooks/{id}
    Unsubscribe
Server security

mTLS and scoped keys

Mutual TLS, with API keys scoped per environment and permission. Keys rotate without downtime.

IP allowlisting

Requests are accepted only from allowlisted server IPs. Others are rejected at the gateway.

Idempotency keys

A retry with the same key does not create a duplicate wallet or transaction.

Rate limits per client

Limits are applied per client and reported in the response headers.

Signed webhooks

Each event carries a signature and timestamp for verification on receipt.

Exportable audit log

API calls, policy decisions and signatures are recorded and can be exported.

Support

Support runs around the clock in three levels, with response and resolution times set out in your SLA. Covers the SDKs, the REST API and webhooks, and the backend Texavio runs for them.

L1

Service desk

First response on every ticket, around the clock: triage, how-to questions, and account and access issues.

L2

Technical support

Configuration, integration and module issues investigated by product engineers, with workarounds while a fix is prepared.

L3

Engineering

Bug fixes, root-cause analysis and security patches from Antier's core engineering team.

  • 24×7 coverage
  • SLA-backed response and resolution
  • Escalation from L1 to L3
  • Updates until every incident is closed
Get started

  • React Native and Node.js SDKs
  • REST API + webhooks
  • Pay-as-you-go
No-code option

Wallet SaaS

A branded wallet app hosted by Texavio, with the same modules. Live in 2 weeks.