PolyNode SDKs

PolyNode has official SDKs for TypeScript, Python, and Rust. Each SDK covers the same core product surfaces:

the complete V3 API, including combos and perps data
the real-time settlement stream
the managed orderbook stream, including optional PN1 integrity checks
the V3 perps WebSocket
short-form crypto markets with the correct Chainlink price window

The examples in this section are tested against these published versions:

Language	Package	Current version	Runtime
TypeScript / Node.js	`polynode-sdk`	`0.12.2`	Node.js 18+
Python	`polynode`	`0.12.2`	Python 3.10+
Rust	`polynode`	`0.15.2`	Tokio async runtime

Use these versions or newer. Older releases do not contain the complete V3 registry, the managed perps stream, reconnect-aware settlement delivery, and PN1 orderbook integrity described here.

Install

TypeScript
Python
Rust

npm install polynode-sdk ws

Both ESM import and CommonJS require are supported.

python -m pip install --upgrade "polynode>=0.12.2"

[dependencies]
polynode = "0.15.2"
tokio = { version = "1", features = ["macros", "rt-multi-thread"] }

Create an API key at polynode.dev, then keep it in a server-side environment variable:

export POLYNODE_API_KEY="pn_live_..."

Do not embed a PolyNode API key or wallet private key in browser code, mobile bundles, source control, screenshots, or logs.

First request

This reads V3 platform statistics and does not change any data.

TypeScript
Python
Rust

import { PolyNode } from 'polynode-sdk';

const apiKey = process.env.POLYNODE_API_KEY;
if (!apiKey) throw new Error('Set POLYNODE_API_KEY');

const pn = new PolyNode({ apiKey });
const stats = await pn.v3.stats();
console.log(stats);

import os
from polynode import PolyNode

with PolyNode(api_key=os.environ["POLYNODE_API_KEY"]) as pn:
    stats = pn.v3.execute("GET /v3/stats")
    print(stats)

use polynode::{PolyNodeClient, V3RequestOptions};

#[tokio::main]
async fn main() -> polynode::Result<()> {
    let api_key = std::env::var("POLYNODE_API_KEY")
        .expect("Set POLYNODE_API_KEY");
    let client = PolyNodeClient::new(api_key)?;
    let stats = client
        .v3()
        .execute_named("GET /v3/stats", V3RequestOptions::default())
        .await?;
    println!("{stats:#}");
    Ok(())
}

Choose a surface

V3 API

Query wallets, trades, positions, combos, fees, builders, webhooks, and perps through the complete 120-operation registry.

Settlement stream

Receive pending settlements and confirmation updates with typed events, filters, reconnect replay, and observable overflow.

Short-form and TWAP

Follow 5-minute, 15-minute, 1-hour, and 4-hour crypto markets as their slugs and Chainlink windows rotate.

Orderbook stream

Consume raw books or maintain verified local state with PN1 sequence and checksum validation.

Perps stream

Stream tickers, best bid/offer, complete books, trades, statistics, and 1-minute or 1-hour candles.

Trading and fees

Place current V2 orders, configure builder attribution, and understand which fee fields belong on the wire.

Core parity

Capability	TypeScript	Python	Rust
Complete V3 registry	`pn.v3.operations`	`pn.v3.operations`	`client.v3().operations()`
Execute any registered V3 route	`pn.v3.execute()`	`pn.v3.execute()`	`execute_named()`
Settlement reconnect cursor and overlap dedupe	Yes	Yes	Yes
Unknown additive events remain available	Yes	Yes	Yes
5m / 15m / 1h / 4h managed market rotation	Yes	Yes	Yes
Explicit Chainlink 30s / 60s TWAP filters	Yes	Yes	Yes
PN1 orderbook integrity	Yes	Yes	Yes
Managed V3 perps WebSocket	Yes	Yes	Yes
Current V2 trading default	Yes	Yes	Yes, `trading` feature

Some optional helpers are intentionally language-specific. The SQLite local cache is currently available in TypeScript and Rust; trading dependencies are optional in Python and Rust. Those differences do not affect the core surfaces above.

Three different WebSockets

The SDKs expose separate clients because the streams have different protocols and state:

Stream	Use it for	SDK entry point
Events	settlements, confirmations, wallet activity, combos, Chainlink prices	`pn.ws` / `client.stream(...)`
Orderbook	prediction-market depth and trades	`pn.orderbook`, `OrderbookEngine`, or `client.orderbook_stream(...)`
Perps	perps tickers, BBO, books, trades, statistics, klines	`pn.perps` / `client.perps_stream()`

Do not send an event-stream subscription to the orderbook or perps socket. Each guide starts from the correct client and includes shutdown code.

Next steps

TypeScript

Node.js setup and complete examples.

Python

Synchronous REST and asynchronous streams.

Rust

Tokio clients, typed events, and feature flags.

If you prefer HTTP or raw WebSockets, use the API overview, event WebSocket guide, orderbook protocol, and perps API.

Getting Started

Core Guides

Optional Helpers

TypeScript

Python

Rust

Charts (Browser)

Install

First request

Choose a surface

V3 API

Settlement stream

Short-form and TWAP

Orderbook stream

Perps stream

Trading and fees

Core parity

Three different WebSockets

Next steps

TypeScript

Python

Rust

​Install

​First request

​Choose a surface

V3 API

Settlement stream

Short-form and TWAP

Orderbook stream

Perps stream

Trading and fees

​Core parity

​Three different WebSockets

​Next steps

TypeScript

Python

Rust

Install

First request

Choose a surface

Core parity

Three different WebSockets

Next steps