supanovasupanovaDOCS
Open Launchpad
Launchpad documentation
market data

One token by its CIP-56 instrument id.

GET /api/v1/market/tokens/{assetId}. One token by its CIP-56 instrument id.

Anonymous calls are accepted under a per-IP budget; an X-API-Key raises the limit. When the deployment sets MARKET_DATA_REQUIRE_API_KEY=true the key becomes mandatory and anonymous calls answer 401 MARKET_DATA_API_KEY_REQUIRED.

Request

GET /api/v1/market/tokens/{assetId}

The schema permits anonymous access. Supported credentials: a customer API key with read scope in X-API-Key. Deployment policy can require a key for market-data routes.

Parameters

NameInTypeRequiredConstraintsDescription
assetIdpathstringYesmax length: 128; pattern: ^[A-Za-z0-9][A-Za-z0-9._-]{0,127}$—
X-Request-IdheaderstringNomin length: 8; max length: 128; pattern: ^[A-Za-z0-9._:-]+$Optional client correlation identifier. The server always generates a separate authoritative request ID and retains a valid supplied value only as secondary audit correlation metadata.

cURL

Set ASSET_ID to the path and required query values before running this example. URL-encode path values as needed.

bash
curl --fail-with-body --silent --show-error \
  --request GET \
  --url "https://launch-api.supanova.app/api/v1/market/tokens/${ASSET_ID}" \
  --header "X-API-Key: $SUPANOVA_API_KEY"

Responses

200

Token.

HeaderTypeDescription
X-Request-IdstringServer-generated request correlation identifier to retain for support and reconciliation.

Content type: application/json

Type: object.

FieldTypeRequiredConstraintsDescription
itemobject · Schema 1Yes——
metaobject · Schema 2Yes——

Additional fields are not allowed.

400

The request is malformed or failed validation. Codes: VALIDATION_FAILED, AMBIGUOUS_CREDENTIALS.

HeaderTypeDescription
X-Request-IdstringServer-generated request correlation identifier to retain for support and reconciliation.

Content type: application/json

Standard envelope: error.code, error.message, optional error.details, and requestId. See error handling and the full code registry.

401

Unknown API key, or a key is required. Also: API_KEY_INVALID, API_KEY_REVOKED, MARKET_DATA_API_KEY_REQUIRED.

HeaderTypeDescription
X-Request-IdstringServer-generated request correlation identifier to retain for support and reconciliation.

Content type: application/json

Standard envelope: error.code, error.message, optional error.details, and requestId. See error handling and the full code registry.

403

The credential may not call this route. Codes: API_KEY_IP_NOT_ALLOWED, PRODUCT_ACCOUNT_RESTRICTED.

HeaderTypeDescription
X-Request-IdstringServer-generated request correlation identifier to retain for support and reconciliation.

Content type: application/json

Standard envelope: error.code, error.message, optional error.details, and requestId. See error handling and the full code registry.

404

Unknown asset.

HeaderTypeDescription
X-Request-IdstringServer-generated request correlation identifier to retain for support and reconciliation.

Content type: application/json

Standard envelope: error.code, error.message, optional error.details, and requestId. See error handling and the full code registry.

429

The caller exceeded an IP or principal request budget.

HeaderTypeDescription
Retry-AfterintegerWhole seconds to wait before retrying a rate-limited request.
X-Request-IdstringServer-generated request correlation identifier to retain for support and reconciliation.

Content type: application/json

Standard envelope: error.code, error.message, optional error.details, and requestId. See error handling and the full code registry.

503

The PQS market projection is not configured.

HeaderTypeDescription
X-Request-IdstringServer-generated request correlation identifier to retain for support and reconciliation.

Content type: application/json

Standard envelope: error.code, error.message, optional error.details, and requestId. See error handling and the full code registry.

default

Machine-readable API error. The HTTP status identifies the error class.

HeaderTypeDescription
X-Request-IdstringServer-generated request correlation identifier to retain for support and reconciliation.

Content type: application/json

Standard envelope: error.code, error.message, optional error.details, and requestId. See error handling and the full code registry.

Nested schemas

Field links above lead to the complete nested object, array, and variant definitions below. Required fields are scoped to their containing object.

Schema 1

Response 200.item

Type: object.

FieldTypeRequiredConstraintsDescription
asset_idstringYes——
circulating_supplystringYespattern: ^-?\d+(?:\.\d+)?$Tokens outside the pools: total supply minus the curve's unsold inventory and liquidity reserve, or minus the AMM token reserve after graduation.
created_atstringYes——
decimalsintegerYesminimum: -9007199254740991; maximum: 9007199254740991—
descriptionstringYes——
fdvstringYespattern: ^-?\d+(?:\.\d+)?$Fully diluted value in CC: price x total_supply.
fdv_usdone or more variants · Schema 3Yes——
holders_countintegerYesminimum: -9007199254740991; maximum: 9007199254740991—
image_urlstring or nullYes——
instrument_adminstringYes——
instrument_idstringYes——
market_capone or more variants · Schema 4Yes—Circulating market cap in CC: price x circulating_supply (fdv x circulating_supply / total_supply).
market_cap_usdone or more variants · Schema 3Yes——
namestringYes——
pairsarray of string · Schema 5Yes——
pricestringYespattern: ^-?\d+(?:\.\d+)?$—
price_usdone or more variants · Schema 3Yes——
slugstringYes——
stagestringYesallowed: "graduating", "ignition", "in_orbit", "near_escape"—
symbolstringYes——
total_supplystringYespattern: ^-?\d+(?:\.\d+)?$—
websitestring or nullYes——

Additional fields are not allowed.

Schema 2

Response 200.meta

Type: object.

FieldTypeRequiredConstraintsDescription
as_ofstringYes——
cc_usdone or more variants · Schema 6Yes——
ledger_offsetstringYes——
network_idstringYes——
source"pqs"Yes——

Additional fields are not allowed.

Schema 3

Response 200.item.fdv_usd

Type: one or more variants.

At least one of these variants must match:

  • Variant 1: string. pattern: ^-?\d+(?:\.\d+)?$
  • Variant 2: null.

Schema 4

Response 200.item.market_cap

Type: one or more variants.

Circulating market cap in CC: price x circulating_supply (fdv x circulating_supply / total_supply).

At least one of these variants must match:

  • Variant 1: string. pattern: ^-?\d+(?:\.\d+)?$
  • Variant 2: null.

Schema 5

Response 200.item.pairs

Type: array of string.

Array items: string.

Schema 6

Response 200.meta.cc_usd

Type: one or more variants.

At least one of these variants must match:

  • Variant 1: object · Schema 7.
  • Variant 2: null.

Schema 7

Response 200.meta.cc_usd variant 1

Type: object.

FieldTypeRequiredConstraintsDescription
as_ofstringYes——
ratestringYespattern: ^-?\d+(?:\.\d+)?$—
sourcestringYes——
stalebooleanYes——

Additional fields are not allowed.

Source contract

This page is generated from the checked-in customer OpenAPI snapshot. Download JSON, download YAML, or compare the live API reference. Snapshot provenance records the retrieval date and checksum.

Generated from the public API contractDeveloper settings