FORGE

DEVELOPER API / V1

Forge data.
As JSON.

A read-only API over Forge’s on-chain state: launches, creators, vesting schedules and the platform report. Every figure is read from finalized Solana mainnet accounts. No endpoint can sign, trade or move funds.

Access and limits

TierHowPer minutePer day
AnonymousNo header30 per IP—
Free keyX-API-Key: fk_…300 per key20,000 per key

Base URL https://api.launchwithforge.com. Responses carry X-RateLimit-Limit, X-RateLimit-Remaining and X-API-Tier. Data refreshes from the chain at most every five minutes; lookups are cached for one minute. Raw amounts are integer strings in base units — divide by the asset’s decimals. Any origin may call /v1 from a browser, but keep keys out of public front-end code.

Endpoints

GETReturns
/v1/reportPlatform totals: launches by pairing asset, curve volume, fees accrued and uncollected, factory launches, buyback status, incidents.
/v1/launchesAll Forge curve launches, sorted by mint. Filters: status (curve, awaiting-migration, migrated), quote (SOL, TSLAx, NVDAx…), creator. Paging: limit (1–100, default 50) and cursor = the previous page’s nextCursor.
/v1/creators/{address}Every curve and factory launch created by an address.
/v1/vesting/{address}Vesting schedules naming the address as beneficiary, with unlocked and claimable amounts at the current chain time.
curl https://api.launchwithforge.com/v1/launches?status=migrated&limit=20 \
  -H "X-API-Key: fk_your_key"

Errors are JSON {"error": "…"}: 400 invalid input, 401 unknown or revoked key, 404 unknown endpoint, 429 rate limit, 503 chain data temporarily unavailable.

Your API keys

Keys belong to the wallet that signs for them — no account or password. Each action asks your wallet to sign a short, readable message; nothing is sent on chain and no SOL is spent. A wallet can hold up to three active keys. Forge stores only a hash of each key and shows it once.

Connect a wallet to manage its API keys.