Application API
The current application exposes its public launch endpoints through the Next.js origin and proxies launch mutations to the Fastify launch service where required.
| Endpoint | Purpose |
|---|---|
POST /api/launches/pending | Create/reuse a pending launch record and metadata package before wallet submission. |
POST /api/launches/confirm | Submit a pending launch ID and transaction hash for independent receipt verification. |
POST /api/launches/:pendingId/failed | Verify a failed/reverted submission path; browser claims alone are not authoritative. |
GET /api/launches | Paginated/filterable/searchable confirmed launch list. |
GET /api/launches/:token | Exact confirmed launch lookup by token. |
GET /api/assets/:id | Public token image asset. |
GET /api/metadata/:id | Public immutable token metadata JSON. |
GET /api/indexer-health | Current chain/indexing health summary. |
GET /api/backend-health | Backend/database/service health summary. |
Confirmation trust model
The client submits only correlation data such as pendingLaunchId and txHash. The backend fetches and verifies the transaction receipt from LiteForge, checks the expected LaunchManager and decodes the real LaunchCreated event before confirming the record.
Interface stability
These are current application endpoints rather than a versioned third-party public API guarantee. Integrators should treat them as application interfaces unless/until Flipit publishes a stable external API contract.