Skip to main content
There are two parts to an Etherfuse integration, and they use different tools:
  1. The Etherfuse REST API (v2, at the API root, plus /lookup and /auth): call it over HTTP from any language. See Calling the REST API below.
  2. The on-chain Stablebond layer (Solana): when a flow needs bond data or on-chain transactions, use the Stablebond SDKs.

​
Stablebond SDKs

These are open-source clients for the Etherfuse Stablebond program on Solana. They help you query available bonds, read bond data, and work with on-chain transactions. The interactive tutorials in these docs use the TypeScript SDK.
The Stablebond SDKs are Solana on-chain clients. They do not call the Etherfuse REST API, including the v2 endpoints. Use them alongside the REST API for the on-chain part of a flow.

TypeScript

@etherfuse/stablebond-sdk: for JavaScript/TypeScript apps (web and mobile). Retrieve available bonds, read bond data, and perform on-chain transactions.

Rust

stablebond-sdk: for Rust projects needing direct, typed access to the Stablebond program (querying bonds, building transactions).

​
Calling the REST API

The Etherfuse API is a standard HTTP API, so you can call it from any language with an HTTP client. You do not need an SDK. Send your API key in the Authorization header (see Authentication):
Every endpoint in the API reference, for example List payment accounts, has a “Try it” playground with code samples in cURL, JavaScript, Python, and more. To generate a typed client or import into Postman or Insomnia, download the OpenAPI specs: openapi-v2.json covers the v2 endpoints, and openapi.json includes the authentication, organization, customer, KYC, asset, lookup and statement endpoints.
Building with an AI assistant? Connect the MCP server so Claude, ChatGPT, or any MCP-compatible client can search these docs and the API reference.