Bitpont API Quickstart | First Request & SDK Setup

Start with a read

Download the JavaScript client into your server project. It has no package dependencies and is not published to npm. Use a current Node.js runtime with fetch; Bitpont’s server is tested on Node.js 24.

1. Start without a key using publicAccess: true.
2. Call the integration manifest and choose a ready public market resource.
3. Read the result and preserve its source timestamp and availability state.
4. Respect Retry-After and use bounded refresh intervals.

Account reads, swap quotes and unsigned treasury preparation require scoped partner access. See free access and limits before choosing your integration.

import { BitpontClient } from './bitpont-client.mjs';

const bitpont = new BitpontClient({
  publicAccess: true
});
const manifest = await bitpont.integrationManifest();
const marketRead = manifest.resources.find(
  item => item.id === 'hyperliquid.markets'
);
if (!marketRead?.ready) throw new Error('Market read unavailable');

const result = await bitpont.read('hyperliquid.markets', {kind:'perp'});
console.log(result.state, result.observedAt, result.data);

Check before adding a feature

integrationManifest() separates an adapter being configured from your key being authorized. A ready adapter can still return unavailable provider data. The manifest performs no blockchain health check and establishes no trading eligibility.

Read the response, not just HTTP 200

Read results carry state, servedAt, observedAt, freshness, pagination and data. A response can be partial or stale. A null observation time means the source time is unknown; it does not mean the data is current.

Choose your next integration

Use the market guide for discovery, the portfolio guide for existing positions or the treasury guide for unsigned payment proposals. Website owners can start with the public discovery widget without an API key.