Introduction

Snekfun’s public APIs

APIs

Snekfun exposes several public HTTP APIs. Pick the one that matches what you’re building.

Snekfun Provider API

https://analytics.snek.fun

Main-page pool lists, per-token pool state, orders, AI pools, asset metadata, user history, and WebSocket Protocol v2 streams.

Charts WS Server

https://charts.snek.fun/v1

Historical and initial OHLC / market-cap bars over HTTP; live bars over WebSocket (LastBar / MCapBar).

Transaction Builder API

https://builder.snek.fun

Build, sign, and submit Snek.fun transactions — orders (routed to the bonding curve or AMM automatically), token launches, order cancels, and vesting locks.

UTXO Monitor

https://utxo-monitor.snek.fun

Lightweight endpoint that returns unspent outputs for a wallet — used alongside the Transaction Builder when composing transactions client-side.

Balances API

https://analytics.snek.fun/balances

Holders, PnL cards, and aggregate balances in ADA for payment key hashes. HTTP only (no WebSocket).

Snekfun API (vesting)

https://token-vesting.snek.fun

Unspent vesting rows by redeemer or by asset. HTTP only (no WebSocket).

See Authentication and Rate limits for behavior that applies across these APIs.

Common identifiers

Asset ID

Most endpoints accept an asset or assetId parameter. This is a Cardano native-asset identifier in the format:

{policyId}.{hex-encoded asset name}

Part	Description	Example
policyId	56-character hex string — the minting policy hash	fbd4d3c334063ac19566f6ba39b6ec707ea91fa81d0c09201575c10b
.	Dot separator	.
Asset name	Hex-encoded token name (UTF-8 → hex)	44415645 (= DAVE)

Full example:

fbd4d3c334063ac19566f6ba39b6ec707ea91fa81d0c09201575c10b.44415645

ADA itself has no policy ID and is represented as "." (a single dot) in pool and trade payloads.

Payment-key hash (PKH)

Many endpoints accept a pkh parameter — the 56-character hex hash of a wallet’s payment verification key. You can derive it from any Cardano addr1… address.