> ## Documentation Index > Fetch the complete documentation index at: https://shield.fi/docs/llms.txt > Use this file to discover all available pages before exploring further. # List market transactions > Read public market transactions with cursor pagination. ## OpenAPI ````yaml openapi.json GET /explore/transactions openapi: 3.1.0 info: title: Shield Swap API description: >- Shield Swap REST API for pools, positions, routes, quotes, and settlement status. Transactions target the configured shield_swap program and `token_registry.aleo`. ## Numeric wire format Exact financial values are JSON strings, not JSON numbers. Unsigned decimal inputs use ASCII digits and an optional `.` fraction, for example `"1234.50"`; base-unit integers use ASCII digits only. Grouping separators, localized decimal commas, signs, exponent notation, whitespace, Unicode digits, and redundant leading zeros are not accepted for those inputs. Signed response metrics may include a leading `-`. Clients should localize only for display and convert user input back to this canonical form before sending it. ## Authentication Most endpoints require credentials from a wallet that has accepted the current terms of use (recorded by `/auth/verify`). Public routes are `/health`, `/ready`, `/metrics`, `POST /auth/challenge`, `POST /auth/verify`, `/protocol/state`, `/compliance*`, `GET /tokens`, `GET /pools`, `GET /pools/stats`, `GET /pools/{key}`, `GET /pools/{key}/ohlcv`, `GET /pools/{key}/liquidity-distribution`, `GET /pools/{key}/trades`, `GET /pools/{key}/stats`, `GET /pools/{key}/oracle`, `GET /explore/*`, and `/geckoterminal/*`. Browsers use HTTP-only session cookies issued by `/auth/verify`. Access sessions last 15 minutes and are renewed through `/auth/refresh`. Programmatic clients use a long-lived token from `POST /api-tokens` as `Authorization: Bearer ss_…`. API tokens cover data and trading routes and can request WebSocket tickets. Token management, code redemption, and admin routes require a browser session. ## WebSocket feed The live feed runs on the separate websocket gateway at `GET /ws`. 1. Request a ticket from `GET /auth/ws-ticket` using a browser session or API token. 2. Open the socket and send the `authenticate` frame within 5 seconds. 3. Subscribe to each required room. 4. Before the 60-second ticket expires, request a new ticket and send another `authenticate` frame. The socket accepts WebSocket tickets only. Session JWTs and API tokens are rejected. ```json {"action": "authenticate", "token": ""} {"action": "subscribe", "room": "trades:"} {"action": "unsubscribe", "room": ""} {"action": "synchronize"} ``` After reconnecting, resend subscriptions and then send `synchronize`. The gateway replies `{"control": "synchronized"}` when those subscriptions are active. Refetch any REST data that depends on the stream after receiving the reply. Each connection allows 32 rooms, 240 client frames per minute, and 2 KB per frame. A client may subscribe only to the balance room for its ticket subject. Rooms: - `pool_launches`: newly created pools - `pool_stats:`: price & liquidity updates - `ohlcv:`: candle updates - `trades:`: swaps / mints / burns - `balances:
`: balance-change hints for an address - `protocol_config`: revisioned protocol-configuration invalidations Server messages are either events (`{"type": , "data": { … }}`) or control messages (`{"control": }`). Event types are `PoolLaunch`, `PoolStats`, `Ohlcv`, `Trade`, `BalanceChange`, and `ProtocolConfigChanged`. Its data contains `revision`, `observed_block`, and the changed `scope`/`key` pairs. Financial fields use the numeric format described above. Treat `ProtocolConfigChanged` as an invalidation, not as the new configuration. Fetch `GET /protocol/state?minimum_revision=`; retry a `503 protocol_revision_pending` after the advertised `Retry-After`; and discard or requote any `/route` result whose `protocol_revision` is older. Subscribe to `pool_stats:` separately when live price and liquidity updates matter. The gateway currently sends `synchronized` and `resync_required` controls. `resync_required` means the stream may have missed updates, so refetch affected data over REST. Ignore unknown control values. Event delivery is at most once. Treat REST as the source of truth. During a deployment the gateway may close the socket with code 1012 (service restart); reconnect and restore the subscriptions. contact: name: Shield Swap license: name: '' version: 0.1.0 servers: - url: https://api.swap.shield.fi description: Shield Swap mainnet API security: [] tags: - name: auth description: Wallet sign-in, sessions, logout, and WebSocket tickets - name: api-tokens description: >- Long-lived API tokens for programmatic access; send as `Authorization: Bearer ss_…` on any gated endpoint - name: referral description: >- Referral code redemption, attribution, activity logging, and administration - name: pools description: Pool metadata, stats, trades, OHLCV - name: positions description: LP positions - name: tokens description: Token registry - name: explore description: Market-wide token, pool, and transaction discovery - name: compliance description: Token/pair allowlist, pause, and pool-creation gating state - name: protocol description: Fee tiers and tick spacings - name: route description: Swap routing - name: unclaimed description: Pending swap outputs and position fees - name: geckoterminal description: Public GeckoTerminal integration data - name: airdrop description: >- Faucet: sends ALEO, USDCx, and ETH to a user address as records, once per address per 15 min - name: debug description: On-chain introspection helpers paths: /explore/transactions: get: tags: - explore summary: List market transactions operationId: explore_list_transactions parameters: - name: window in: query description: 'Feed window: 1h, 1d, 1w, or 1m' required: false schema: type: string - name: type in: query description: 'Transaction type: swap, mint, or burn' required: false schema: type: string - name: token in: query description: Token symbol, name, or address required: false schema: type: string - name: pool in: query description: Pool key required: false schema: type: string - name: cursor in: query description: Cursor from the prior response required: false schema: type: string - name: limit in: query description: Page size (1-100) required: false schema: type: integer format: int64 responses: '200': description: Market transaction feed content: application/json: schema: $ref: '#/components/schemas/ExploreTransactionListResponseDoc' '400': description: Invalid query parameters content: application/json: schema: $ref: '#/components/schemas/ErrorResponseDoc' '500': description: Internal server error content: application/json: schema: $ref: '#/components/schemas/ErrorResponseDoc' components: schemas: ExploreTransactionListResponseDoc: type: object required: - data properties: data: type: array items: $ref: '#/components/schemas/ExploreTransactionDoc' nextCursor: type: - string - 'null' ErrorResponseDoc: type: object required: - error properties: code: type: - string - 'null' error: type: string ref: type: - string - 'null' ExploreTransactionDoc: type: object required: - id - tradeType - amount0 - amount1 - executedAt - transactionHash - poolId - poolKey - token0 - token1 - token0Symbol - token1Symbol - token0Decimals - token1Decimals properties: amount0: type: string amount1: type: string executedAt: type: string id: type: string poolId: type: string poolKey: type: string token0: type: string token0Decimals: type: integer format: int32 token0Symbol: type: string token1: type: string token1Decimals: type: integer format: int32 token1Symbol: type: string tradeType: type: string transactionHash: type: string ````