One pair with its full figures.

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/pairs/{pairId}

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

Name	In	Type	Required	Constraints	Description
`pairId`	path	string	Yes	max length: `160`; pattern: `^[A-Za-z0-9][A-Za-z0-9._-]{0,127}:(?:curve\|amm)$`	<instrument id>:curve or :amm
`X-Request-Id`	header	string	No	min 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 PAIR_ID to the path and required query values before running this example. URL-encode path values as needed.

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

Responses

200

Pair.

Header	Type	Description
`X-Request-Id`	string	Server-generated request correlation identifier to retain for support and reconciliation.

Content type: application/json

Type: object.

Field	Type	Required	Constraints	Description
`item`	object · Schema 1	Yes	—	—
`meta`	object · Schema 2	Yes	—	—

Additional fields are not allowed.

400

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

Header	Type	Description
`X-Request-Id`	string	Server-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.

Header	Type	Description
`X-Request-Id`	string	Server-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.

Header	Type	Description
`X-Request-Id`	string	Server-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 pair.

Header	Type	Description
`X-Request-Id`	string	Server-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.

Header	Type	Description
`Retry-After`	integer	Whole seconds to wait before retrying a rate-limited request.
`X-Request-Id`	string	Server-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.

Header	Type	Description
`X-Request-Id`	string	Server-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.

Header	Type	Description
`X-Request-Id`	string	Server-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.

Field	Type	Required	Constraints	Description
`base`	object · Schema 3	Yes	—	—
`created_at`	string or null	Yes	—	—
`created_at_block`	string or null	Yes	—	—
`created_at_txn_id`	string or null	Yes	—	—
`fdv`	string	Yes	pattern: `^-?\d+(?:\.\d+)?$`	—
`fdv_usd`	one or more variants · Schema 4	Yes	—	—
`fee_bps`	integer	Yes	minimum: `-9007199254740991`; maximum: `9007199254740991`	—
`graduation`	object · Schema 5	Yes	—	—
`holders_count`	integer	Yes	minimum: `-9007199254740991`; maximum: `9007199254740991`	—
`last_trade_at`	string or null	Yes	—	—
`liquidity`	object · Schema 6	Yes	—	—
`market`	string	Yes	—	—
`market_cap`	one or more variants · Schema 7	Yes	—	Circulating market cap in CC: price x circulating_supply (fdv x circulating_supply / total_supply).
`market_cap_usd`	one or more variants · Schema 4	Yes	—	—
`pair_id`	string	Yes	—	—
`price`	string	Yes	pattern: `^-?\d+(?:\.\d+)?$`	—
`price_change`	object · Schema 8	Yes	—	—
`price_usd`	one or more variants · Schema 4	Yes	—	—
`quote`	object · Schema 3	Yes	—	—
`status`	string	Yes	allowed: `"active"`, `"graduated"`	—
`ts`	integer	Yes	minimum: `-9007199254740991`; maximum: `9007199254740991`	—
`txns`	object · Schema 9	Yes	—	—
`venue`	string	Yes	allowed: `"amm"`, `"curve"`	—
`volume`	object · Schema 8	Yes	—	—
`volume_usd`	object · Schema 10	Yes	—	—

Additional fields are not allowed.

Schema 2

Response 200.meta

Type: object.

Field	Type	Required	Constraints	Description
`as_of`	string	Yes	—	—
`cc_usd`	one or more variants · Schema 11	Yes	—	—
`ledger_offset`	string	Yes	—	—
`network_id`	string	Yes	—	—
`source`	`"pqs"`	Yes	—	—

Additional fields are not allowed.

Schema 3

Response 200.item.base

Type: object.

Field	Type	Required	Constraints	Description
`asset_id`	string	Yes	—	—
`instrument_admin`	string or null	Yes	—	—
`name`	string	Yes	—	—
`symbol`	string	Yes	—	—

Additional fields are not allowed.

Schema 4

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 5

Response 200.item.graduation

Type: object.

Field	Type	Required	Constraints	Description
`percent`	string	Yes	pattern: `^-?\d+(?:\.\d+)?$`	—
`stage`	string	Yes	allowed: `"graduating"`, `"ignition"`, `"in_orbit"`, `"near_escape"`	—
`threshold_cc`	string	Yes	pattern: `^-?\d+(?:\.\d+)?$`	—

Additional fields are not allowed.

Schema 6

Response 200.item.liquidity

Type: object.

Field	Type	Required	Constraints	Description
`cc`	string	Yes	pattern: `^-?\d+(?:\.\d+)?$`	—
`reserves`	object · Schema 12	Yes	—	—
`usd`	one or more variants · Schema 4	Yes	—	—

Additional fields are not allowed.

Schema 7

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 8

Response 200.item.price_change

Type: object.

Field	Type	Required	Constraints	Description
`h1`	string	Yes	pattern: `^-?\d+(?:\.\d+)?$`	—
`h24`	string	Yes	pattern: `^-?\d+(?:\.\d+)?$`	—
`h6`	string	Yes	pattern: `^-?\d+(?:\.\d+)?$`	—
`m5`	string	Yes	pattern: `^-?\d+(?:\.\d+)?$`	—

Additional fields are not allowed.

Schema 9

Response 200.item.txns

Type: object.

Field	Type	Required	Constraints	Description
`h1`	object · Schema 13	Yes	—	—
`h24`	object · Schema 13	Yes	—	—
`h6`	object · Schema 13	Yes	—	—
`m5`	object · Schema 13	Yes	—	—

Additional fields are not allowed.

Schema 10

Response 200.item.volume_usd

Type: object.

Field	Type	Required	Constraints	Description
`h1`	one or more variants · Schema 4	Yes	—	—
`h24`	one or more variants · Schema 4	Yes	—	—
`h6`	one or more variants · Schema 4	Yes	—	—
`m5`	one or more variants · Schema 4	Yes	—	—

Additional fields are not allowed.

Schema 11

Response 200.meta.cc_usd

Type: one or more variants.

At least one of these variants must match:

Variant 1: object · Schema 14.
Variant 2: null.

Schema 12

Response 200.item.liquidity.reserves

Type: object.

Field	Type	Required	Constraints	Description
`base`	string	Yes	pattern: `^-?\d+(?:\.\d+)?$`	—
`quote`	string	Yes	pattern: `^-?\d+(?:\.\d+)?$`	—

Additional fields are not allowed.

Schema 13

Response 200.item.txns.h1

Type: object.

Field	Type	Required	Constraints	Description
`buys`	integer	Yes	minimum: `-9007199254740991`; maximum: `9007199254740991`	—
`sells`	integer	Yes	minimum: `-9007199254740991`; maximum: `9007199254740991`	—

Additional fields are not allowed.

Schema 14

Response 200.meta.cc_usd variant 1

Type: object.

Field	Type	Required	Constraints	Description
`as_of`	string	Yes	—	—
`rate`	string	Yes	pattern: `^-?\d+(?:\.\d+)?$`	—
`source`	string	Yes	—	—
`stale`	boolean	Yes	—	—

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.

Request#

Parameters

cURL

Responses#

200

400

401

403

404

429

503

default

Nested schemas#

Schema 1

Schema 2

Schema 3

Schema 4

Schema 5

Schema 6

Schema 7

Schema 8

Schema 9

Schema 10

Schema 11

Schema 12

Schema 13

Schema 14

Source contract#

Request

Responses

Nested schemas

Source contract