Socket
Book a DemoInstallSign in
Socket
Book a DemoInstallSign in

@avalanche-sdk/data

Package Overview
Dependencies
Maintainers
0
Versions
15
Alerts
File Explorer

Advanced tools

License
Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@avalanche-sdk/data

@avalanche-sdk/data The Avalanche Data SDK is a powerful and flexible toolset designed to simplify the integration with Avalanche's suite of blockchain services.

latest
Source
npmnpm
Version
0.5.3
Version published
Maintainers
0
Created
Source

@avalanche-sdk/data

The Avalanche Data SDK is a powerful and flexible toolset designed to simplify the integration with Avalanche's suite of blockchain services.

Currently, this SDK is focused on providing robust support for Data APIs.

Summary

Data API: The Data API provides web3 application developers with multi-chain data related to Avalanche's primary network, Avalanche subnets, and Ethereum. With Data API, you can easily build products that leverage real-time and historical transaction and transfer history, native and token balances, and various types of token metadata. The API is in Beta and may be subject to change.

If you have feedback or feature requests for the API, please submit them here. Bug reports can be submitted here, and any potential security issues can be reported here.

Table of Contents

SDK Installation

The SDK can be installed with either npm, pnpm, bun or yarn package managers.

NPM

npm add @avalanche-sdk/data

PNPM

pnpm add @avalanche-sdk/data

Bun

bun add @avalanche-sdk/data

Yarn

yarn add @avalanche-sdk/data zod

# Note that Yarn does not install peer dependencies automatically. You will need
# to install zod as shown above.

[!NOTE] This package is published with CommonJS and ES Modules (ESM) support.

Model Context Protocol (MCP) Server

This SDK is also an installable MCP server where the various SDK methods are exposed as tools that can be invoked by AI applications.

Node.js v20 or greater is required to run the MCP server from npm.

Claude installation steps

Add the following server definition to your claude_desktop_config.json file:

{
  "mcpServers": {
    "Avalanche": {
      "command": "npx",
      "args": [
        "-y", "--package", "@avalanche-sdk/data",
        "--",
        "mcp", "start",
        "--api-key", "...",
        "--chain-id", "...",
        "--network", "..."
      ]
    }
  }
}
Cursor installation steps

Create a .cursor/mcp.json file in your project root with the following content:

{
  "mcpServers": {
    "Avalanche": {
      "command": "npx",
      "args": [
        "-y", "--package", "@avalanche-sdk/data",
        "--",
        "mcp", "start",
        "--api-key", "...",
        "--chain-id", "...",
        "--network", "..."
      ]
    }
  }
}

You can also run MCP servers as a standalone binary with no additional dependencies. You must pull these binaries from available Github releases:

curl -L -o mcp-server \
    https://github.com/{org}/{repo}/releases/download/{tag}/mcp-server-bun-darwin-arm64 && \
chmod +x mcp-server

If the repo is a private repo you must add your Github PAT to download a release -H "Authorization: Bearer {GITHUB_PAT}".

{
  "mcpServers": {
    "Todos": {
      "command": "./DOWNLOAD/PATH/mcp-server",
      "args": [
        "start"
      ]
    }
  }
}

For a full list of server arguments, run:

npx -y --package @avalanche-sdk/data -- mcp start --help

Requirements

For supported JavaScript runtimes, please consult RUNTIMES.md.

SDK Example Usage

Example

import { Avalanche } from "@avalanche-sdk/data";

const avalanche = new Avalanche();

async function run() {
  const result = await avalanche.data.healthCheck();

  console.log(result);
}

run();

Authentication

Per-Client Security Schemes

This SDK supports the following security scheme globally:

NameTypeScheme
apiKeyapiKeyAPI key

To authenticate with the API the apiKey parameter must be set when initializing the SDK client instance. For example:

import { Avalanche } from "@avalanche-sdk/data";

const avalanche = new Avalanche({
  apiKey: "<YOUR_API_KEY_HERE>",
});

async function run() {
  const result = await avalanche.data.healthCheck();

  console.log(result);
}

run();

Available Resources and Operations

Available methods

data

data.evm.address.balances

data.evm.address.chains

  • list - List all chains associated with a given address

data.evm.address.contracts

data.evm.address.transactions

data.evm.blocks

data.evm.chains

  • list - List chains
  • get - Get chain information
  • getAddressChains - [Deprecated] Gets a list of all chains where the address was either a sender or receiver in a transaction or ERC transfer. The list is currently updated every 15 minutes.

⚠️ This operation will be removed in a future release. Please use /v1/address/:address/chains endpoint instead . :warning: Deprecated

⚠️ This operation will be removed in a future release. Please use /v1/transactions endpoint instead . :warning: Deprecated

  • listAllLatestBlocks - [Deprecated] Lists the latest blocks for all supported EVM chains. Filterable by network.

⚠️ This operation will be removed in a future release. Please use /v1/blocks endpoint instead . :warning: Deprecated

data.evm.contracts

data.evm.transactions

data.icm

data.nfts

  • reindex - Reindex NFT metadata
  • list - List tokens
  • get - Get token details

data.operations

data.primaryNetwork

data.primaryNetwork.balances

data.primaryNetwork.blocks

data.primaryNetwork.rewards

data.primaryNetwork.transactions

data.primaryNetwork.utxos

data.primaryNetwork.vertices

data.signatureAggregator

  • aggregate - Aggregate Signatures
  • get - Get Aggregated Signatures

data.teleporter

⚠️ This operation will be removed in a future release. Please use /v1/icm/messages/:messageId endpoint instead . :warning: Deprecated

⚠️ This operation will be removed in a future release. Please use /v1/icm/messages endpoint instead . :warning: Deprecated

⚠️ This operation will be removed in a future release. Please use /v1/icm/addresses/:address/messages endpoint instead . :warning: Deprecated

data.usageMetrics

  • getUsage - Get usage metrics for the Data API
  • getLogs - Get logs for requests made by client
  • getSubnetRpcUsage - Get usage metrics for the Subnet RPC
  • getRpcUsageMetrics - [Deprecated] Gets metrics for public Subnet RPC usage over a specified time interval aggregated at the specified time-duration granularity.

⚠️ This operation will be removed in a future release. Please use /v1/subnetRpcUsageMetrics endpoint instead. :warning: Deprecated

Standalone functions

All the methods listed above are available as standalone functions. These functions are ideal for use in applications running in the browser, serverless runtimes or other environments where application bundle size is a primary concern. When using a bundler to build your application, all unused functionality will be either excluded from the final bundle or tree-shaken away.

To read more about standalone functions, check FUNCTIONS.md.

Available standalone functions

⚠️ This operation will be removed in a future release. Please use /v1/address/:address/chains endpoint instead . :warning: Deprecated

⚠️ This operation will be removed in a future release. Please use /v1/blocks endpoint instead . :warning: Deprecated

⚠️ This operation will be removed in a future release. Please use /v1/transactions endpoint instead . :warning: Deprecated

⚠️ This operation will be removed in a future release. Please use /v1/icm/messages/:messageId endpoint instead . :warning: Deprecated

⚠️ This operation will be removed in a future release. Please use /v1/icm/messages endpoint instead . :warning: Deprecated

⚠️ This operation will be removed in a future release. Please use /v1/icm/addresses/:address/messages endpoint instead . :warning: Deprecated

  • dataUsageMetricsGetRpcUsageMetrics - [Deprecated] Gets metrics for public Subnet RPC usage over a specified time interval aggregated at the specified time-duration granularity.

⚠️ This operation will be removed in a future release. Please use /v1/subnetRpcUsageMetrics endpoint instead. :warning: Deprecated

Global Parameters

Certain parameters are configured globally. These parameters may be set on the SDK client instance itself during initialization. When configured as an option during SDK initialization, These global values will be used as defaults on the operations that use them. When such operations are called, there is a place in each to override the global value, if needed.

For example, you can set chainId to "43114" at SDK initialization and then you do not have to pass the same value on calls to operations like getNative. But if you want to do so you may, which will locally override the global setting. See the example code below for a demonstration.

Available Globals

The following global parameters are available.

NameTypeDescription
chainIdstringA supported EVM chain id, chain alias, or blockchain id.
networkcomponents.GlobalParamNetworkA supported network type mainnet or testnet/fuji.

Example

import { Avalanche } from "@avalanche-sdk/data";

const avalanche = new Avalanche({
  chainId: "43114",
  network: "mainnet",
});

async function run() {
  const result = await avalanche.data.evm.address.balances.getNative({
    blockNumber: "6479329",
    address: "0x71C7656EC7ab88b098defB751B7401B5f6d8976F",
    currency: "usd",
  });

  console.log(result);
}

run();

Pagination

Some of the endpoints in this SDK support pagination. To use pagination, you make your SDK calls as usual, but the returned response object will also be an async iterable that can be consumed using the for await...of syntax.

Here's an example of one such pagination call:

import { Avalanche } from "@avalanche-sdk/data";

const avalanche = new Avalanche({
  chainId: "43114",
});

async function run() {
  const result = await avalanche.data.evm.address.balances.listErc20({
    blockNumber: "6479329",
    address: "0x71C7656EC7ab88b098defB751B7401B5f6d8976F",
    contractAddresses:
      "0xB31f66AA3C1e785363F0875A1B74E27b85FD66c7, 0x49D5c2BdFfac6CE2BFdB6640F4F80f226bc10bAB",
    currency: "usd",
  });

  for await (const page of result) {
    console.log(page);
  }
}

run();

Retries

Some of the endpoints in this SDK support retries. If you use the SDK without any configuration, it will fall back to the default retry strategy provided by the API. However, the default retry strategy can be overridden on a per-operation basis, or across the entire SDK.

To change the default retry strategy for a single API call, simply provide a retryConfig object to the call:

import { Avalanche } from "@avalanche-sdk/data";

const avalanche = new Avalanche();

async function run() {
  const result = await avalanche.data.healthCheck({
    retries: {
      strategy: "backoff",
      backoff: {
        initialInterval: 1,
        maxInterval: 50,
        exponent: 1.1,
        maxElapsedTime: 100,
      },
      retryConnectionErrors: false,
    },
  });

  console.log(result);
}

run();

If you'd like to override the default retry strategy for all operations that support retries, you can provide a retryConfig at SDK initialization:

import { Avalanche } from "@avalanche-sdk/data";

const avalanche = new Avalanche({
  retryConfig: {
    strategy: "backoff",
    backoff: {
      initialInterval: 1,
      maxInterval: 50,
      exponent: 1.1,
      maxElapsedTime: 100,
    },
    retryConnectionErrors: false,
  },
});

async function run() {
  const result = await avalanche.data.healthCheck();

  console.log(result);
}

run();

Error Handling

AvalancheError is the base class for all HTTP error responses. It has the following properties:

PropertyTypeDescription
error.messagestringError message
error.statusCodenumberHTTP response status code eg 404
error.headersHeadersHTTP response headers
error.bodystringHTTP body. Can be empty string if no body is returned.
error.rawResponseResponseRaw HTTP response
error.data$Optional. Some errors may contain structured data. See Error Classes.

Example

import { Avalanche } from "@avalanche-sdk/data";
import * as errors from "@avalanche-sdk/data/models/errors";

const avalanche = new Avalanche({
  chainId: "43114",
});

async function run() {
  try {
    await avalanche.data.nfts.reindex({
      address: "0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E",
      tokenId: "145",
    });
  } catch (error) {
    // The base class for HTTP error responses
    if (error instanceof errors.AvalancheError) {
      console.log(error.message);
      console.log(error.statusCode);
      console.log(error.body);
      console.log(error.headers);

      // Depending on the method different errors may be thrown
      if (error instanceof errors.BadRequestError) {
        console.log(error.data$.message); // errors.BadRequestMessage
        console.log(error.data$.statusCode); // number
        console.log(error.data$.error); // string
      }
    }
  }
}

run();

Error Classes

Primary errors:

  • AvalancheError: The base class for HTTP error responses.
    • BadRequestError: Bad requests generally mean the client has passed invalid or malformed parameters. Error messages in the response could help in evaluating the error. Status code 400.
    • UnauthorizedError: When a client attempts to access resources that require authorization credentials but the client lacks proper authentication in the request, the server responds with 401. Status code 401.
    • ForbiddenError: When a client attempts to access resources with valid credentials but doesn't have the privilege to perform that action, the server responds with 403. Status code 403.
    • NotFoundError: The error is mostly returned when the client requests with either mistyped URL, or the passed resource is moved or deleted, or the resource doesn't exist. Status code 404.
    • TooManyRequestsError: This error is returned when the client has sent too many, and has hit the rate limit. Status code 429.
    • InternalServerError: The error is a generic server side error that is returned for any uncaught and unexpected issues on the server side. This should be very rare, and you may reach out to us if the problem persists for a longer duration. Status code 500.
    • BadGatewayError: This is an internal error indicating invalid response received by the client-facing proxy or gateway from the upstream server. Status code 502.
    • ServiceUnavailableError: The error is returned for certain routes on a particular Subnet. This indicates an internal problem with our Subnet node, and may not necessarily mean the Subnet is down or affected. Status code 503.
Less common errors (6)

Network errors:

Inherit from AvalancheError:

  • ResponseValidationError: Type mismatch between the data returned from the server and the structure expected by the SDK. See error.rawValue for the raw value and error.pretty() for a nicely formatted multi-line string.

Server Selection

Override Server URL Per-Client

The default server can be overridden globally by passing a URL to the serverURL: string optional parameter when initializing the SDK client instance. For example:

import { Avalanche } from "@avalanche-sdk/data";

const avalanche = new Avalanche({
  serverURL: "https://glacier-api.avax.network",
});

async function run() {
  const result = await avalanche.data.healthCheck();

  console.log(result);
}

run();

Custom HTTP Client

The TypeScript SDK makes API calls using an HTTPClient that wraps the native Fetch API. This client is a thin wrapper around fetch and provides the ability to attach hooks around the request lifecycle that can be used to modify the request or handle errors and response.

The HTTPClient constructor takes an optional fetcher argument that can be used to integrate a third-party HTTP client or when writing tests to mock out the HTTP client and feed in fixtures.

The following example shows how to use the "beforeRequest" hook to to add a custom header and a timeout to requests and how to use the "requestError" hook to log errors:

import { Avalanche } from "@avalanche-sdk/data";
import { HTTPClient } from "@avalanche-sdk/data/lib/http";

const httpClient = new HTTPClient({
  // fetcher takes a function that has the same signature as native `fetch`.
  fetcher: (request) => {
    return fetch(request);
  }
});

httpClient.addHook("beforeRequest", (request) => {
  const nextRequest = new Request(request, {
    signal: request.signal || AbortSignal.timeout(5000)
  });

  nextRequest.headers.set("x-custom-header", "custom value");

  return nextRequest;
});

httpClient.addHook("requestError", (error, request) => {
  console.group("Request Error");
  console.log("Reason:", `${error}`);
  console.log("Endpoint:", `${request.method} ${request.url}`);
  console.groupEnd();
});

const sdk = new Avalanche({ httpClient });

Debugging

You can setup your SDK to emit debug logs for SDK requests and responses.

You can pass a logger that matches console's interface as an SDK option.

[!WARNING] Beware that debug logging will reveal secrets, like API tokens in headers, in log messages printed to a console or files. It's recommended to use this feature only during local development and not in production.

import { Avalanche } from "@avalanche-sdk/data";

const sdk = new Avalanche({ debugLogger: console });

Development

Maturity

This SDK is in beta, and there may be breaking changes between versions without a major version update. Therefore, we recommend pinning usage to a specific package version. This way, you can install the same version each time without breaking changes unless you are intentionally looking for the latest version.

Contributions

While we value open-source contributions to this SDK, this library is generated programmatically. Any manual changes added to internal files will be overwritten on the next generation. We look forward to hearing your feedback. Feel free to open a PR or an issue with a proof of concept and we'll do our best to include it in a future release.

FAQs

Package last updated on 06 Aug 2025

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

Identifying and Preventing Fraudulent Engineering Candidates: An Investigation into 80 Confirmed Cases

Research

/

Security News

Identifying and Preventing Fraudulent Engineering Candidates: An Investigation into 80 Confirmed Cases

Socket identified 80 fake candidates targeting engineering roles, including suspected North Korean operators, exposing the new reality of hiring as a security function.

By Lauren Valencia, Kirill Boychenko  -  Sep 17, 2025