Get the open candle and the last closed candle of a token for one interval.
GET /api/v1/tokens/{slug}/candles/latest. Get the open candle and the last closed candle of a token for one interval.
Request
GET /api/v1/tokens/{slug}/candles/latest
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 |
|---|---|---|---|---|---|
slug | path | string | Yes | min length: 1; max length: 64; pattern: ^[a-z0-9](?:[a-z0-9-]{0,62}[a-z0-9])?$ | — |
interval | query | string | No | default: 1h; allowed: "1m", "5m", "1h", "4h", "1d" | — |
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 SLUG 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/tokens/${SLUG}/candles/latest" \
--header "X-API-Key: $SUPANOVA_API_KEY"Responses
200
Open and last closed candle.
| 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 |
|---|---|---|---|---|
interval | string | Yes | allowed: "1m", "5m", "1h", "4h", "1d" | — |
lastClosed | one or more variants · Schema 1 | Yes | — | — |
latest | one or more variants · Schema 1 | Yes | — | — |
meta | object · Schema 2 | Yes | — | — |
Additional fields are not allowed.
400
Invalid token slug or interval. Also: 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
Credentials are missing, malformed, expired or revoked. Codes: API_KEY_INVALID, API_KEY_REVOKED.
| 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
Token not found.
| 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 stage 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.lastClosed
Type: one or more variants.
At least one of these variants must match:
- Variant 1: object · Schema 3.
- Variant 2: null.
Schema 2
Response 200.meta
Type: object.
| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
provenance | object · Schema 4 | Yes | — | — |
schemaVersion | "1" | Yes | — | — |
Additional fields are not allowed.
Schema 3
Response 200.lastClosed variant 1
Type: object.
| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
close | string | Yes | pattern: ^(?:0|[1-9]\d{0,27})(?:\.\d{1,40})?$ | — |
high | string | Yes | pattern: ^(?:0|[1-9]\d{0,27})(?:\.\d{1,40})?$ | — |
low | string | Yes | pattern: ^(?:0|[1-9]\d{0,27})(?:\.\d{1,40})?$ | — |
open | string | Yes | pattern: ^(?:0|[1-9]\d{0,27})(?:\.\d{1,40})?$ | — |
time | string | Yes | format: date-time; pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d(?:\.\d+)?(?:Z|([+-](?:[01]\d|2[0-3]):[0-5]\d)))$ | — |
volume | string | Yes | pattern: ^(?:0|[1-9]\d{0,27})(?:\.\d{1,10})?$ | — |
Additional fields are not allowed.
Schema 4
Response 200.meta.provenance
Type: object.
| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
asOf | string | Yes | format: date-time; pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d(?:\.\d+)?(?:Z|([+-](?:[01]\d|2[0-3]):[0-5]\d)))$ | — |
dataMode | string | Yes | allowed: "projected", "simulated" | — |
disclaimer | string | Yes | min length: 1 | — |
label | string | Yes | min length: 1 | — |
networkId | string | Yes | pattern: ^canton:[-_a-zA-Z0-9]{1,32}$ | — |
visibility | string | Yes | allowed: "aggregated-from-entitled-views", "public-by-design" | — |
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.