supanovasupanovaDOCS
Open Launchpad
Launchpad documentation
configuration

Return the safe runtime and feature configuration for the frontend.

GET /api/v1/app-config. Return the safe runtime and feature configuration for the frontend.

Request

GET /api/v1/app-config

The schema permits anonymous access.

Parameters

NameInTypeRequiredConstraintsDescription
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

bash
curl --fail-with-body --silent --show-error \
  --request GET \
  --url "https://launch-api.supanova.app/api/v1/app-config"

Responses

200

Only public, non-secret configuration.

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

Content type: application/json

Type: object.

FieldTypeRequiredConstraintsDescription
apiVersion"v1"Yes——
appStagestringYesallowed: "local", "preview", "devnet", "mainnet"—
authobject · Schema 1Yes——
capabilitiesobject · Schema 2Yes——
cantonNetworkIdstringYes——
contractVersion"2026-08-17.2"Yes——
featuresobject · Schema 3Yes——
productLegalobject · Schema 4Yes——
releaseone or more variants · Schema 5Yes——
service"supanova-superapp-backend"Yes——

Additional fields are not allowed.

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.

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.auth

Type: object.

FieldTypeRequiredConstraintsDescription
customerProvidersarray of string · Schema 6Yes——
transport"bearer"Yes——
workforceProvider"supabase"Yes——

Additional fields are not allowed.

Schema 2

Response 200.capabilities

Type: object.

FieldTypeRequiredConstraintsDescription
accountClosureobject · Schema 7Yes——
activityobject · Schema 7Yes——
cantonExecutionobject · Schema 7Yes——
creatorProjectionobject · Schema 7Yes——
customAvatarUploadobject · Schema 7Yes——
dappBridgeobject · Schema 7Yes——
depositInstructionsobject · Schema 7Yes——
depositInitiationobject · Schema 7Yes——
issuerDocumentsobject · Schema 7Yes——
favoritesSyncobject · Schema 7Yes——
launchApplicationsobject · Schema 7Yes——
launchCreationobject · Schema 7Yes——
launchParticipationobject · Schema 7Yes——
launchMediaobject · Schema 7Yes——
marketDataobject · Schema 7Yes——
marketStreamingobject · Schema 7Yes——
marketingEmailobject · Schema 7Yes——
missionControlobject · Schema 7Yes——
novaAirdropobject · Schema 7Yes——
novaWaitlistobject · Schema 7Yes——
operationsobject · Schema 7Yes——
pendingTransfersobject · Schema 7Yes——
personalTradeHistoryobject · Schema 7Yes——
pointsLeaderboardobject · Schema 7Yes——
pointsProgramobject · Schema 7Yes——
portfolioValuationobject · Schema 7Yes——
productAnalyticsobject · Schema 7Yes——
portfolioobject · Schema 7Yes——
referenceRatesobject · Schema 7Yes——
referralsobject · Schema 7Yes——
restrictedVaultobject · Schema 7Yes——
supportobject · Schema 7Yes——
supportCasesobject · Schema 7Yes——
swapsobject · Schema 7Yes——
transactionDetailsobject · Schema 7Yes——
transferPreapprovalsobject · Schema 7Yes——
transfersobject · Schema 7Yes——
transactionalEmailobject · Schema 7Yes——
usdcxRoutingobject · Schema 7Yes——
walletVerificationobject · Schema 7Yes——

Additional fields are not allowed.

Schema 3

Response 200.features

Type: object.

FieldTypeRequiredConstraintsDescription
activitybooleanYes——
adminPreviewbooleanYes——
cantonMockbooleanYes——
catalogbooleanYes——
launchCreationbooleanYes——
launchApplicationsbooleanYes——
launchMarketbooleanYes——
launchMediabooleanYes——
novaWaitlistbooleanYes——
launchParticipationbooleanYes——
portfoliobooleanYes——
swapsbooleanYes——
transfersbooleanYes——

Additional fields are not allowed.

Schema 4

Response 200.productLegal

Type: object.

FieldTypeRequiredConstraintsDescription
documentsarray of unspecified · Schema 8Yesmin items: 3; max items: 3—
effectiveAt"2026-08-04T00:00:00.000Z"Yes——
id"supanova-product-access-legal"Yes——
legalApproval"required-before-connected-release"Yes——
reacceptance"material-version-only"Yes——
setDigest"sha256:b07f64b9f408addf88588d529535451f0421aadaecc665a5e461406597ce77b2"Yes——
updatedAt"2026-08-12T00:00:00.000Z"Yes——
version"1"Yes——

Additional fields are not allowed.

Schema 5

Response 200.release

Type: one or more variants.

At least one of these variants must match:

  • Variant 1: "development".
  • Variant 2: string. pattern: ^(?:[0-9a-f]{40}|[0-9a-f]{64}|sha256:[0-9a-f]{64})$

Schema 6

Response 200.auth.customerProviders

Type: array of string.

Array items: string. allowed: "mock", "privy", "supabase"

Schema 7

Response 200.capabilities.accountClosure

Type: object.

FieldTypeRequiredConstraintsDescription
dataModestringYesallowed: "none", "projected", "simulated"—
reasonCodestring or nullYes——
statusstringYesallowed: "blocked", "disabled", "preview", "ready"—

Additional fields are not allowed.

Schema 8

Response 200.productLegal.documents

Type: array of unspecified.

min items: 3; max items: 3

Tuple positions (in order):

  1. object · Schema 9.
  2. object · Schema 10.
  3. object · Schema 11.

Schema 9

Response 200.productLegal.documents position 1

Type: object.

FieldTypeRequiredConstraintsDescription
action"agree"Yes——
digest"sha256:ae3001c9110291ba6d97fe27343218a23ec93427ac7f7654e45e77b3fe08523d"Yes——
slug"terms"Yes——

Additional fields are not allowed.

Schema 10

Response 200.productLegal.documents position 2

Type: object.

FieldTypeRequiredConstraintsDescription
action"acknowledge"Yes——
digest"sha256:5cdce14744e77bd382a30b10469918d64b556c62af995ab1c84601304446ab5f"Yes——
slug"privacy"Yes——

Additional fields are not allowed.

Schema 11

Response 200.productLegal.documents position 3

Type: object.

FieldTypeRequiredConstraintsDescription
action"acknowledge"Yes——
digest"sha256:3d54b4c54d38211c9cb5b5789e97607bd7c49157f7cff5928d2e348c66d04c84"Yes——
slug"risk"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.

Generated from the public API contractDeveloper settings