stonfi_api_client

Thin typed wrapper for the STON.fi API v1 and public export endpoints.

Use this crate when an application needs typed access to STON.fi assets, pools, farms, routers, swap/liquidity simulation, wallet views, stats, transactions, or public export feeds. The crate does not execute swaps or manage transaction submission; application code owns wallet signing, retries around business workflows, persistence, and fallback behavior.

Usage

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

The minimum supported Rust version (MSRV) is 1.88.

Run requests inside an async Tokio runtime. Pass request parameter structs directly where Into<V1Request> or Into<ExportRequest> is implemented, and match response enums with a wildcard arm.

use stonfi_api_client::api_client::StonfiApiClient;
use stonfi_api_client::v1::{PoolsParams, V1Response};

# async fn example() -> Result<(), Box<dyn std::error::Error>> {
let client = StonfiApiClient::builder().build()?;
let response = client.v1.exec(PoolsParams::new()).await?;

match response {
    V1Response::Pools(pools) => {
        println!("pools: {}", pools.pool_list.len());
    }
    _ => {
        println!("unexpected STON.fi response variant");
    }
}
# Ok(())
# }

Use ExportApiClient for public export feeds:

use stonfi_api_client::api_client::StonfiApiClient;
use stonfi_api_client::export::{ExportRequest, ExportResponse};

# async fn example() -> Result<(), Box<dyn std::error::Error>> {
let client = StonfiApiClient::builder().build()?;
let response = client.export.exec(ExportRequest::Cmc).await?;

match response {
    ExportResponse::Cmc(pools) => println!("CMC pools: {}", pools.len()),
    _ => println!("unexpected STON.fi export response variant"),
}
# Ok(())
# }

Supported Endpoints

Public request and response types are marked #[non_exhaustive] for semver headroom. Build public POD structs with Default::default().with_<field>(...) or request parameter new() constructors, pass request parameters directly to V1ApiClient::exec or ExportApiClient::exec where Into<V1Request> or Into<ExportRequest> is implemented, and include a wildcard arm when matching response enums.

Live API tests hit STON.fi directly. Asset metadata, pool counts, prices, transaction state, and optional transaction fields can drift with upstream data.