API
Last updated
Was this helpful?
Last updated
Was this helpful?
To reduce the friction of creating launchpads and launching tokens we have released an API, allowing builders to create their own launchpad contract and users to launch tokens via their launchpad with no-wallet/no-gas API calls.
There is no requirement for a wallet to be connected and instead a user can Flaunch a token connected to their email address, X (Twitter), Farcaster account or Base wallet address.
The account connected to the flaunched token will be able to connect to Flaunch, or any external flow, using to have access to their launchpad fee or coin fee claims and offramp their fees into either crypto or fiat.
So whether you're extending your existing platform to benefit from token launches, or building a more generic plugin that an entire ecosystem can use, the Flaunch API should have ample logic to support you.
No API keys are required for the use of the Web 2 API endpoint. If you are hitting the current rate limits for increased access.
To demonstrate the power of this API, we have put together a landing page that will allow for fast flaunching across multiple recipient types.
Below we have documented the API calls that are available for the Memecoin API. These are also available as a Postman collection for quicker prototyping.
GET
/livez
Checks if the API is running and returns the network configuration.
Headers
Content-Type
application/json
Response
POST
/api/v1/{{ base | base-sepolia }}/create-revenue-manager
Required Fields
protocolFee
Protocol fee in basis points (0-10000, where 100 = 1%)
Fee Recipient Options (MUST choose one)
recipientAddress
Ethereum wallet address for the fee recipient
recipientEmail
Email address for the fee recipient
recipientTwitterUsername
Twitter username (without @ symbol)
recipientFarcasterUsername
Farcaster username (without the @ symbol)
Optional Fields
ownerAddress
Ethereum address that will own the revenue manager (defaults to fee recipient below)
Headers
Content-Type
application/json
Body
Response
POST
/api/v1/upload-image
Uploads and validates an image before creating a memecoin. Images are checked for appropriate content and stored on IPFS.
Headers
Content-Type
application/json
Body
Response
POST
/api/v1/{{ base | base-sepolia }}/launch-memecoin
Creates a new memecoin token on the selected network with the following default parameters:
$10k starting market cap
60% of the total supply for fair launch
80% dev / 20% community split
No revenue manager
After a token has been flaunched, a jobId
will be returned in the response. This jobId
signifies its position in a queue to be flaunched. It can then be referenced when querying the launch-status
endpoint to retrieve the status of the token and subsequent deployed contract address of the token.
Required Fields
name
Token name.
symbol
Token symbol (max 8 characters).
description
Token description.
imageIpfs
IPFS hash from the image upload endpoint.
Creator Authentication Options (MUST choose one)
creatorAddress
Ethereum address to receive creator benefits.
creatorEmail
Email address to create a managed wallet via Privy.
creatorTwitterUsername
Twitter username for verification and wallet creation.
creatorFarcasterUsername
Farcaster username for verification and wallet creation.
If no creator authentication option is provided, the creator fees will go to the Flaunch.gg wallet.
Optional Fields
revenueManagerAddress
Ethereum address of a deployed revenue manager (must be valid address format)
marketCap
Initial market cap in USDC (default: 10,000 = 10000000000)
creatorFeeSplit
Creator fee allocation in basis points (default: 8000 = 80%)
fairLaunchDuration
Duration of fair launch in seconds (default: 1800 = 30 minutes)
fairLaunchSupply
Amount of tokens for fair launch (default: 60% of initial supply = 6000)
websiteUrl
Website URL
telegramUrl
Telegram group URL
discordUrl
Discord server URL
twitterUrl
Twitter/X URL
Headers
Content-Type
application/json
Body
Response
GET
/api/v1/launch-status/{{ jobId }}
Retrierves the launch status of a jobId
.
Headers
Content-Type
application/json
Response