Market data

Prices, fees and history
on the same key

An exchange connector, a mempool parser and your own candle storage are three integrations and three ways to break. Here it is one call, next to the same nodes.

56 ms
Response · p50
1 s
Refresh step
99.99%
Uptime · 30 days
100M
Calls a day

Quotes

api.settla.net/v1/market/quotes

Stream

  • BitcoinBTCBTC-USD$104,789+1.88% · 24h
  • EthereumETHETH-USD$3,939−0.06% · 24h
  • SolanaSOLSOL-USD$214.56+0.71% · 24h
  • TronTRXTRX-USD$0.3142−0.16% · 24h

Volume · 24h $61.2B

History

The series your own chart is drawn from.

Candles, volume and the change over the window arrive in one request. No stitching several sources together, no storage of your own — the response already has the shape a chart expects.

$104,820

+1.88% over the window · 24H

Volume $1.4B

$104,820 · now

−23h−15h−8hnow

Drag across the chart or use the arrow keys

Request

GET https://api.settla.net/v1/market/candles?symbol=BTC-USD&interval=1h&limit=24

Response · selected candle

{
  "symbol": "BTC-USD",
  "interval": "1h",
  "count": 24,
  "candles": [
    …
    {
      "t": "2026-01-01T00:00:00Z",
      "o": 104556.80,
      "h": 104960.72,
      "l": 104529.71,
      "c": 104820.00,
      "v": 1366115421
    }
    …
  ]
}

Endpoints

Three calls cover the market side of the product.

Each answers for every asset you ask about at once, so the loop over coins stays in your code instead of on the wire.

  • GETapi.settla.net/v1/market/quotes

    Quotes

    Spot price, 24-hour change and volume. Fiat conversion is a query parameter, not a second service.

    Response fields

    • price
    • change24h
    • volume24h
    • updatedAt
  • GETapi.settla.net/v1/market/fees

    Fee estimate

    Network rate for three speeds and the expected wait — before the transaction reaches the mempool.

    Response fields

    • economy
    • normal
    • fast
    • eta
  • GETapi.settla.net/v1/market/candles

    Candles and history

    Series from one hour to one week, two years deep: reporting, reconciliation and charts in your UI.

    Response fields

    • t
    • o
    • h
    • l
    • c
    • v
  • One symbol set

    Symbols, precision and timestamps are normalised — a Tron response reads exactly like a Bitcoin one.

  • Freshness attached

    Every value carries the timestamp of its source: you see not only what the price is, but how new it is.

  • Outliers removed

    Prices are aggregated across venues with anomaly filtering, so one exchange glitching never reaches your interface.

  • The same key

    Market calls use the key and the quota you already have for RPC. No second secret and no second invoice.

Fee estimate

api.settla.net/v1/market/fees?chain=bitcoin

Fee

0.00001550 BTC

Network rate
11.1 sat/vB
In dollars
$1.63
Wait
20 min

Fees

What the transfer will cost — before it leaves.

The estimate comes from the state of the network and is converted into fiat at the current price, so it can be shown to the user as it is.

The same answer goes to the wallet before signing: the user sees the fee up front, not on the receipt.

How it is built

The path of a number from venue to your response.

Nothing is forwarded as received. There are four steps between the source and your request, and we can account for each one.

  1. 01

    Sources

    Several venues plus our own nodes. No price ever comes from a single place.

  2. 02

    Filtering

    Stale quotes and outliers are cut by median instead of being averaged in together with the failure.

  3. 03

    Normalisation

    Symbols, precision and time are brought to one shape, so the response never depends on where the value came from.

  4. 04

    Serving

    The finished value sits in the cache of the region nearest to you, so a response takes milliseconds instead of a trip to an exchange.

56 ms
Median response
1 s
Refresh step
2 years
History depth
99.99%
Uptime

Questions

What teams ask first

Infrastructure shouldn't be the thing slowing you down.

Free to start. No credit card required.