Transaction & Market Data APIs

Parsed transaction objects commonly include:

What you typically get

Acceso exposes transactions as structured objects. You do not need to decode raw instruction blobs.

Transaction data

This page covers transaction-level activity and derived market data. The goal is “parsed, queryable, consistent”.

• signature

• slot and block_time

• status (success / error)

• fee_lamports

• accounts involved

• token_transfers (mint, source, destination, amounts)

• program_invocations (program id + instruction name when known)

Parsing is versioned and isolated from the gateway. This keeps behavior stable as programs evolve.

Example: fetch a transaction by signature

curl -sS \
  -H "Authorization: Bearer $ACCESO_API_KEY" \
  "https://<YOUR_ACCESO_API_HOST>/v1/solana/tx/<SIGNATURE>?commitment=finalized"

Common knobs:

For wallets, you usually want a paginated feed. Acceso supports cursor-based pagination where available.

Account activity feeds

Example: transaction response (shape)

{
  "success": true,
  "data": {
    "signature": "5wB...JtS",
    "slot": 285001234,
    "block_time": 1765939001,
    "status": "success",
    "fee_lamports": "5000",
    "token_transfers": [
      {
        "mint": "So11111111111111111111111111111111111111112",
        "source": "Fh8...A1",
        "destination": "9xQ...Tg4",
        "raw_amount": "1000000000",
        "decimals": 9,
        "ui_amount": 1.0
      }
    ]
  },
  "meta": {
    "request_id": "req_9b3d11",
    "timestamp": 1765939200
  }
}

• limit (bounded)

• cursor (opaque)

• commitment

• direction=asc|desc

Data products

Market data is derived from on-chain events. Acceso normalizes cross-DEX behavior into a unified schema.

Market & price data

Typical outputs:

• Spot price estimates per token or pair.

• Trade feed (time, price, size, side).

• OHLCV candles with fixed intervals.

Normalization rules:

• Timestamps use epoch seconds.

• Candle boundaries align to interval edges.

• Volumes use decimal-aware units.

Example: fetch OHLCV candles

curl -sS \
  -H "Authorization: Bearer $ACCESO_API_KEY" \
  "https://<YOUR_ACCESO_API_HOST>/v1/solana/market/candles?base_mint=<MINT>&quote_mint=<MINT>&interval=1m&start=1765935600&end=1765939200"

Market data is an estimate. DEX coverage, route selection, and outlier filtering affect values.

Some endpoints are cached to protect upstream dependencies. Caching is route-dependent.

Caching and consistency

Operational expectation:

• “Latest” endpoints favor freshness but still cap load.

• Historical endpoints favor stability and repeatability.