GET

Price feeds

List feeds

/api/v2/price-feeds

AUTHENTICATIONBearer token · pricing:readService ownermarket-data-serviceContract sourceOpenAPISTATUSProduction listed

Purpose and usage

What this endpoint does

List public feeds plus workspace-owned composites with canonical instruments, provider composition, cadence, aggregation policy, and failover posture.

When to use it

Call this to discover feeds visible to the workspace and compare instruments, providers, cadence, aggregation, and failover policy before selecting one for delivery or valuation.

OUTCOME · Discover

What changes

Read-only projection; it grants no mutation, settlement, traffic, or authority change.

WHY IT MATTERS

Gives people and agents a contract-backed way to discover feeds.
Makes feed provenance, quality, delivery entitlement, replay limits, and workspace-owned composite policy explicit before price data enters valuation or decision workflows.

ISOLATION + AUTHORITY

Instrument, provider, observation, signature, hash-chain, aggregation, composite owner, subscription, delivery, billing, valuation, market, and trading boundaries remain distinct. A feed, snapshot, replay, plan, or subscription supplies data only and grants no oracle-finality, valuation approval, publisher, order, matching, settlement, or trading authority.

BEFORE YOU CALL

Authenticate at the documented boundary: bearer+scope.
Use the live OpenAPI schema as the authority for the exact request shape and response model.
Resolve the canonical instrument and feed, source and aggregation policy, required freshness and quality, and any subscription entitlement or replay window.

WHAT TO DO NEXT

Select a canonical feed identifier and inspect its source composition, normalization, cadence, quality, and failover policy.
Verify the latest signed snapshot or bounded history under the selected feed and any required subscription entitlement.

AGENT GUIDANCE

Use feeds only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
Use the live OpenAPI schema as the authority for the exact request shape and response model.
Preserve decimal values and observation timestamps exactly; distinguish source time, ingestion time, sequence, freshness, health, quality, aggregation, delivery entitlement, and business acceptance.
Use response links and canonical identifiers instead of constructing internal service URLs or scraping the website.

Contract reference

Use the deployed OpenAPI for exact parameters, schemas and security requirements. The tables below provide integration guidance.

Open this operation in OpenAPI

Request and response

Make the request

Examples illustrate integration intent; the referenced OpenAPI operation and component schemas define the executable shape.

PARAMETERS

Headers, path, query, and body

NAMELOCATIONPRESENCETYPE / RULES / PURPOSE

AuthorizationheaderRequired

Bearer tokenCredential containing the pricing:read scope.EXAMPLEBearer hc_live_…

RESPONSES

Status and payload examples

200Public feeds plus private composites visible to the authenticated workspace.Read completed · JSON RESPONSE+

{
  "items": [
    {
      "feed_id": "8c1490adbe524bb79b8be0618e58fe55",
      "name": "BTC / USD composite",
      "mode": "AGGREGATED",
      "cadence_ms": 1000,
      "schema_version": "price-evidence-v1",
      "is_public": true,
      "status": "ACTIVE",
      "instrument": {
        "instrument_id": "56a00e46cfbd4a09a4b087d052fd64be",
        "symbol": "BTC-USD",
        "base_asset": "BTC",
        "quote_asset": "USD",
        "asset_class": "DIGITAL_ASSET"
      },
      "policy": {
        "method": "WEIGHTED_MEDIAN",
        "staleness_threshold_ms": 15000,
        "min_sources": 2,
        "max_deviation_bps": "250",
        "failover_mode": "ALLOW_SINGLE"
      },
      "sources": [
        {
          "provider_id": "0aadf922185145e48e7c87cf3d2759ec",
          "provider_code": "provider-a",
          "provider_name": "Provider A",
          "provider_symbol": "BTCUSD",
          "weight": "1"
        },
        {
          "provider_id": "a754639436a644cf8437da4cfab94242",
          "provider_code": "provider-b",
          "provider_name": "Provider B",
          "provider_symbol": "XBT/USD",
          "weight": "1"
        }
      ]
    }
  ]
}

INTEGRATION DECISION

CALLER ACTION: Accept the returned representation or receipt, then select a canonical feed identifier and inspect its source composition, normalization, cadence, quality, and failover policy.
RETRY SAFETY: Repeat only when the integration needs a fresher authoritative projection.
STATE RECONCILIATION: Use returned identifiers and versions as the comparison point for later reads. Refresh the feed, source mapping, observation timestamp, quality and staleness state, policy version, and delivery or command receipt.

401The bearer credential is missing, expired, or invalid.Authentication required · JSON RESPONSE+

{
  "code": "invalid_credentials",
  "message": "The bearer credential is missing, expired, or invalid."
}

INTEGRATION DECISIONinvalid_credentials

CALLER ACTION: Discard the rejected credential, complete the documented authentication or reassertion flow, and rebuild any request signature with fresh timestamps and nonces.
RETRY SAFETY: Retry only with a newly valid credential and fresh replay-protection values. Do not replay an expired signature.
STATE RECONCILIATION: Authentication failed before an authoritative read was returned for workspace price-feed definitions, source mappings, observations, quality status, subscriptions, and delivery receipts.
ESCALATE WHEN: Escalate when source identity, observation time, confidence, staleness, entitlement, or delivery evidence cannot be reconciled.

403The credential lacks pricing:read or the subscription does not entitle this replay.Authority or policy denied · JSON RESPONSE+

{
  "code": "insufficient_scope",
  "message": "The credential lacks pricing:read or the subscription does not entitle this replay."
}

INTEGRATION DECISIONinsufficient_scope

CALLER ACTION: Verify the exact scope, tenant or workspace membership, owner boundary, step-up purpose, feature policy, and resource eligibility. Never broaden authority automatically.
RETRY SAFETY: Do not retry until the missing authority or policy condition has been deliberately resolved with least privilege.
STATE RECONCILIATION: Confirm the caller and resource resolve to the same authority boundary for workspace price-feed definitions, source mappings, observations, quality status, subscriptions, and delivery receipts.
ESCALATE WHEN: Escalate when source identity, observation time, confidence, staleness, entitlement, or delivery evidence cannot be reconciled.

503The authoritative Core pricing projection is unavailable.Dependency unavailable or outcome uncertain · JSON RESPONSE+

{
  "code": "price_feeds_unavailable",
  "message": "The authoritative Core pricing projection is unavailable."
}

INTEGRATION DECISIONprice_feeds_unavailable

CALLER ACTION: Treat the failure as transient and preserve the last known good representation without presenting it as fresh.
RETRY SAFETY: Retry with bounded exponential backoff and jitter; stop after the integration's failure budget is exhausted.
STATE RECONCILIATION: Refresh the feed, source mapping, observation timestamp, quality and staleness state, policy version, and delivery or command receipt.
ESCALATE WHEN: Escalate when source identity, observation time, confidence, staleness, entitlement, or delivery evidence cannot be reconciled.

OPERATIONAL NOTES

Security and lifecycle guarantees

Start here to resolve a canonical instrument and understand provider composition, cadence, aggregation method, staleness threshold, outlier policy, and failover posture.
DIRECT describes one provider mapping; AGGREGATED describes a governed composite. is_public describes visibility, not fitness or execution authority.
Weights and all observed prices are decimal strings. Preserve them exactly and never infer a feed identifier from a symbol.
The gateway derives workspace ownership and removes internal owner-vault, datastream, and transport counters. No query parameters or request body are accepted; responses are no-store.

Reference version and availability details

This route is implemented in canonical gateway source and appears in the production OpenAPI snapshot observed 2026-10-02T23:27:55.510Z. Authentication, tenant, feature, venue, and market policy still apply.

Verify the exact production OpenAPI operation Return to the V2 directory