Build with supanova
Read Launchpad markets, follow trades, and submit authorized orders through the customer API.
The supanova API gives you token discovery, prices, candles, holder data, account activity, and order submission on Canton. Use the REST API for requests and snapshots, and the market stream for updates.
Start with the right surface
| You want to… | Use |
|---|---|
| Display Launchpad coins and their launch stage | Token discovery |
| Build a screener, chart, or aggregator | Market data |
| Receive trade and price updates | WebSocket stream |
| Read your portfolio and operation status | A customer read key |
| Submit programmatic orders | A trade key and the order flow |
| Inspect every request and response | Public API reference |
API origin
https://launch-api.supanova.appAll customer REST routes use /api/v1. The API serves JSON over HTTPS. Decimal amounts are strings: keep them as strings or use decimal arithmetic rather than JavaScript floating-point numbers.
The schema describes the HTTP contract. Available features also depend on the live deployment. Read GET /api/v1/app-config and check its capability status before offering an action. A route in the reference is not proof that a feature is enabled for the current network or account.
Credentials and authority
Public token discovery can be read without signing in. Use a customer API key for a server integration and for your account's supported read endpoints. Market-data endpoints may require a key.
Trade keys add an Ed25519 request signature and are authorized for one connected Canton Party. They do not authorize withdrawals, transfers, or token launches. Those actions use their own signed-in wallet flows.
Contract files
The live JSON schema and live YAML schema are the machine-readable reference. JSON and YAML snapshots are included with this documentation; their provenance records the source, retrieval date, and JSON checksum.
Generate clients from the customer schema. When the contract changes, review its diff and regenerate your types. Keep a fallback for unknown error codes and additional response fields so additive releases do not break your integration.
Continue with your first API request.