Installation

Install

The SDK is published as @dzapio/sdk. Latest stable: 2.0.44. Targets Node 16+ and modern browsers (see Browser bundler setup). It ships its own wallet libraries — there are no peer dependencies to install separately.

Version pinning

The SDK pins its wallet libraries to exact versions, not ranges:

Dependency	Pinned version
`viem`	`2.48.4`
`ethers`	`5.7.2`
`@solana/web3.js`	`1.95.8`

If your app resolves a different viem, WalletClient becomes a structurally different type and passing a signer stops typechecking — with an error that never mentions versions. Force a single copy:

{
  "overrides": {
    "viem": "2.48.4"
  }
}

{
  "resolutions": {
    "viem": "2.48.4"
  }
}

overrides:
  viem: 2.48.4

The same applies to ethers@5.7.2 if you use the ethers adapter.

Browser bundler setup

The SDK pulls in @solana/web3.js, tonweb and ethers@5, which expect Node globals. In a stock Vite or Next app the build fails or breaks at runtime until Buffer, global and process are polyfilled.

import { defineConfig } from 'vite';
import { nodePolyfills } from 'vite-plugin-node-polyfills';

// npm i -D vite-plugin-node-polyfills
export default defineConfig({
  plugins: [
    nodePolyfills({
      globals: { Buffer: true, global: true, process: true },
    }),
  ],
});

module.exports = {
  webpack: (config, { isServer }) => {
    if (!isServer) {
      config.resolve.fallback = {
        ...config.resolve.fallback,
        fs: false,
        net: false,
        tls: false,
        crypto: require.resolve('crypto-browserify'),
        stream: require.resolve('stream-browserify'),
      };
      config.plugins.push(
        new (require('webpack').ProvidePlugin)({ Buffer: ['buffer', 'Buffer'], process: 'process/browser' }),
      );
    }
    return config;
  },
};

DZapIO/examples is a working Vite + wagmi app with this setup already in place — see its vite.config.ts for a reference configuration.

Wallet adapters

The SDK accepts both viem and ethers.js signers.

import { createWalletClient, http } from 'viem';
import { arbitrum } from 'viem/chains';

const walletClient = createWalletClient({
  account: '0xYourAddress',
  chain: arbitrum,
  transport: http(),
});

import { ethers } from 'ethers';

// The SDK bundles ethers v5, use the v5 provider API
const provider = new ethers.providers.JsonRpcProvider('https://arbitrum.llamarpc.com');
const signer = new ethers.Wallet('0xPrivateKey', provider);

Pass either as the signer field to dzap.trade(), dzap.zap(), etc.

Never put private keys in client code or commit them. Use a wallet provider (RainbowKit, ConnectKit, etc.) on the frontend; use a secrets manager on the backend.

Custom RPC URLs

The SDK ships with sensible defaults but you’ll want your own RPCs for production.

import { DZapClient } from '@dzapio/sdk';

const dzap = DZapClient.getInstance(undefined, {
  1: ['https://eth.llamarpc.com'],
  42161: ['https://arbitrum.llamarpc.com'],
  8453: ['https://base.llamarpc.com'],
});

The first URL in each array is primary; subsequent URLs are fallbacks for read-quorum.

API key (optional)

const dzap = DZapClient.getInstance('dzap_xxxxxxxxxxxxxx');

API keys raise rate limits and unlock per-route configuration. See Authentication and Rate Limits.

@dzapio/sdk

Trade

Zap

Tokens & Balances

Chains

Approvals

Utilities

Reference

Examples

Installation

Install

Version pinning

Browser bundler setup

Wallet adapters

Custom RPC URLs

API key (optional)

Next: Client

​Install

​Version pinning

​Browser bundler setup

​Wallet adapters

​Custom RPC URLs

​API key (optional)

​Next: Client

Install

Version pinning

Browser bundler setup

Wallet adapters

Custom RPC URLs

API key (optional)

Next: Client