API

This API covers the creation of tokens, revenune managers, uploading images.

If you're looking to consume data from the Flaunch API, see the RESTful API section.

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

API Keys

No API keys are required for the use of the Web 2 API endpoint. If you are hitting the current rate limits reach out on discord for increased access.

Example Integration

To demonstrate the power of this API, we have put together a landing page that will allow for fast flaunching across multiple recipient types.

Have you integrated the Flaunch API? Get in touch and we'll feature it here!

Available API Calls

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.

Base API URI

https://web2-api.flaunch.gg

Supported Chains

The :chain segment accepts these slugs. Aliases and numeric chain IDs are rejected with a 400.

Slug

Chain ID

Launch

Fee split at launch

Existing manager

Create manager

base

8453

Yes

base-sepolia

84532

Yes

robinhood

4663

Yes

Fee split at launch works on every chain, including Robinhood. Passing feeSplitRecipients deploys a fee split manager as part of the launch — on Robinhood that is a DynamicAddressFeeSplitManager, on Base a static AddressFeeSplitManager. Recipient shares behave identically either way.

The distinction that matters is which manager gets deployed, not whether managers are supported.

Chain support is machine-readable at /api/v1/config, so you should not need to hardcode this table. Check capabilities there before assuming a chain supports an operation:

"capabilities": {
  "feeSplitLaunch": true,     // feeSplitRecipients at launch
  "existingManager": true,    // revenueManagerAddress / feeSplitManagerAddress
  "standaloneManager": true   // create-revenue-manager / create-fee-split-manager
}

A chain that does not support an operation rejects it with Manager operations are not supported on this chain before any side effect — no metadata is pinned, nothing is queued, and no RPC call is made.

Health Check

GET /livez

Reports the API's dependency health. status is ok when every check passes and degraded otherwise; the endpoint still returns 200 either way.

Headers

Name

Value

Content-Type

application/json

Response

{
  "status": "ok",
  "serverWallet": "0xF1a700000087c011413C21C9b357A6962Aa256f9",
  "checks": {
    "rpc": true,
    "redis": true
  }
}

Service Configuration

GET /api/v1/config

Returns the chains this deployment supports, their capabilities, and whether sandbox launches are accepted. Prefer this over hardcoding chain lists.

Response

{
  "success": true,
  "sandbox": false,
  "chains": [
    {
      "slug": "robinhood",
      "chainId": 4663,
      "name": "Robinhood Chain",
      "nativeCurrency": "ETH",
      "blockExplorerUrl": "https://robinhoodchain.blockscout.com",
      "capabilities": {
        "feeSplitLaunch": true,
        "existingManager": false,
        "standaloneManager": false
      }
    }
  ]
}

Create a Revenue Manager (Launchpad)

POST /api/v1/{{ base | base-sepolia | robinhood }}/create-revenue-manager

Required Fields

Name

Value

protocolFee

Protocol fee in basis points (0-10000, where 100 = 1%)

Fee Recipient Options (MUST choose one)

Name

Value

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

Name

Value

ownerAddress

Ethereum address that will own the revenue manager (defaults to fee recipient below)

Headers

Name

Value

Content-Type

application/json

Body

{
  "protocolFee": "1000",
  "recipientAddress": "0x498E93Bc04955fCBAC04BCF1a3BA792f01Dbaa96",
  "ownerAddress": "0xabcdef123456789abcdef123456789abcdef1234"
}

Response

{
    "success": true,
    "managerAddress": "0x57ac78c4a704233e274bbcdeb057ba640b65de23",
    "txHash": "0x171c6358fabc86337bfe6decc6d2d6fc2fe3ca9918a680ad36b5a71bec34e56e",
    "owner": "0x498E93Bc04955fCBAC04BCF1a3BA792f01Dbaa96",
    "recipientAddress": "0xF1a700000087c011413C21C9b357A6962Aa256f9",
    "protocolFee": 1000,
    "privy": null
}

{
    "success": true,
    "managerAddress": "0xe21ff18247e8816ab447c2f0eec087503105d948",
    "txHash": "0x3b2ea8464286ac85545de12cb7cbf0d56d37d5149855fcb9871337c2873ae6b8",
    "owner": "0x498E93Bc04955fCBAC04BCF1a3BA792f01Dbaa96",
    "recipientAddress": "0xDAc4A85d446B30F21a79c07097dc56Cd4A07E87b",
    "protocolFee": 1000,
    "privy": {
        "privyUserId": "did:privy:cm8prfp7700eh6kf1zduzfhsh",
        "walletAddress": "0xDAc4A85d446B30F21a79c07097dc56Cd4A07E87b"
    }
}

{
  "success": false,
  "error": "Invalid protocol fee. Must be a number between 0 and 10000 (0-100%)"
}

Create a Fee Split Manager (Launchpad)

POST /api/v1/:chain/create-fee-split-manager

Create a reusable fee split manager contract that can be used across multiple token launches.

Required Fields

Name

Type

Description

recipients

Array

Array of fee split recipients (same format as feeSplitRecipients above)

Owner (one required):

ownerAddress

string

Wallet address of the fee split manager owner

ownerEmail

string

Email address of the owner

ownerTwitterUsername

string

Twitter username of the owner

ownerFarcasterUsername

string

Farcaster username of the owner

Creator Share (optional)

creatorShare

number

Optional: Creator share in basis points (0-10000, where 1000 = 10%). Defaults to 0 when not included.

Request Examples:

Basic Fee Split Manager with Wallet Owner:

{
  "recipients": [
    {"type": "email", "id": "founder@example.com"},
    {"type": "twitter", "id": "justinavery"},
    {"type": "wallet", "id": "0x1234567890123456789012345678901234567890"}
  ],
  "creatorShare": 1500 // 15% to creator
  "ownerAddress": "0x9876543210987654321098765432109876543210"
}

Custom Splits with Email Owner:

{
  "recipients": [
    {"type": "email", "id": "founder@example.com", "split": "5000000"},
    {"type": "twitter", "id": "justinavery", "split": "3000000"},
    {"type": "wallet", "id": "0x123...", "split": "2000000"}
  ],
  "creatorShare": 5000 // 50% to creator
  "ownerEmail": "manager@example.com"
}

Success Response

{
  "success": true,
  "message": "Fee split manager created",
  "managerAddress": "0x6baa4ec493a9698dc7388c0f290e29ea3d149f99",
  "txHash": "0x04e594ee46312eecee8827aa2fef777dd2a94d247b723662be3a6daabb300028",
  "owner": "0x9876543210987654321098765432109876543210",
  "recipients": [
    {
      "address": "0x1234567890123456789012345678901234567890",
      "percentage": "33.33333",
      "originalInput": {"type": "email", "id": "founder@example.com"}
    },
    {
      "address": "0xabcdefabcdefabcdefabcdefabcdefabcdefabcd", 
      "percentage": "33.33333",
      "originalInput": {"type": "twitter", "id": "justinavery"}
    },
    {
      "address": "0x1234567890123456789012345678901234567890",
      "percentage": "33.33334",
      "originalInput": {"type": "wallet", "id": "0x1234567890123456789012345678901234567890"}
    }
  ],
  "totalRecipients": 3
}

Token Metadata Upload

The /api/v1/upload-metadata endpoint uploads token metadata to IPFS via Pinata and returns the IPFS hash and token URI. This endpoint is similar to the metadata upload step in the Launch Token flow but is available as a standalone service.

POST /api/v1/upload-metadata

Request Body

{ 
    "name": "string (required)", 
    "symbol": "string (required)", 
    "description": "string (required)", 
    "imageIpfs": "string (required)", 
    "websiteUrl": "string (optional)", 
    "discordUrl": "string (optional)", 
    "twitterUrl": "string (optional)", 
    "telegramUrl": "string (optional)",
}

Parameters

Required.

Name

Value

name

The token name

symbol

The token symbol

description

Token description

imageIpfs

IPFS hash of the token image (without ipfs:// prefix). Use Image Upload endpoint to generate an imageIPFS.

Optional.

Name

Value

websiteUrl

Project website URL

discordUrl

Discord server URL

twitterUrl

Twitter/X profile URL

telegramUrl

Telegram channel/group URL

Response

{ 
    "success": true, 
    "ipfsHash": "QmY7Yh4UquoXHLPFo2XbhXkhBvFoPwmQUSa92pxnxjQuPU", 
    "tokenURI": "ipfs://QmY7Yh4UquoXHLPFo2XbhXkhBvFoPwmQUSa92pxnxjQuPU" 
}

{ 
    "success": false, 
    "error": "Error message describing what went wrong" 
}

Example Usage

Basic Metadata Upload

curl -X POST http://web2-api.flaunch.gg/api/v1/upload-metadata
-H "Content-Type: application/json"
-d '{ "name": "My Token", "symbol": "MTK", "description": "A sample token for demonstration", "imageIpfs": "QmSampleImageHash123", "websiteUrl": "https://mytoken.com", "twitterUrl": "https://twitter.com/mytoken" }'

The endpoint creates ERC-20/ERC-721 compatible metadata with this structure:

  {
    "name": "My Token",
    "description": "A sample token for demonstration",
    "image": "ipfs://QmSampleImageHash123",
    "properties": {
      "websiteUrl": "https://mytoken.com",
      "twitterUrl": "https://twitter.com/mytoken",
    }
  }

Image Upload

POST /api/v1/upload-image

Uploads and validates an image before creating a memecoin. Images are checked for appropriate content and stored on IPFS.

Rate Limit: Maximum 4 image uploads per minute per IP address.

Headers

Name

Value

Content-Type

application/json

Body

{
  // Base64 Encoded Image String (https://www.base64-image.de/)
  "base64Image": "data:image/jpeg;base64,/9j/4AAQSkZJRgAB...FwySj0f/2Q=="
}

Response

{
  "success": true,
  "ipfsHash": "QmX7UbPKJ7Drci3y6p6E8oi5TpUiG7NH3qSzcohPX9Xkvo",
  "tokenURI": "ipfs://QmX7UbPKJ7Drci3y6p6E8oi5TpUiG7NH3qSzcohPX9Xkvo",
  "nsfwDetection": null
}

{
  "success": false,
  "error": "Error message"
}

{
  "success": false,
  "error": "Content flagged: Suggestive content",
  "nsfwDetection": {
    "isNSFW": true,
    "score": 0.92,
    "message": "Content flagged: Suggestive content",
    "details": []
  }
}

Video Upload

Upload a video file to Cloudflare Stream for use in token creation.

POST /api/v1/upload-video

Request Body

Field

Type

Description

maxDurationSeconds

number

Maximum video duration in seconds (default: 300, max: 300)

maxSizeBytes

number

Maximum file size in bytes (default: 52,428,800, max: 52,428,800 = 50MB)

userId

string

User identifier for tracking (default: "anonymous")

Rate Limiting

10 uploads per hour per IP address
API enforces maximum limits of 50MB and 5 minutes duration
Users can specify lower limits via request parameters

Request Example

{
  "maxDurationSeconds": 300,
  "maxSizeBytes": 52428800,
  "userId": "user123"
}

Success Response

{
  "success": true,
  "uploadURL": "https://upload.videodelivery.net/...",
  "videoUID": "c0ee021fd95c4f0d8cc13c70c6172d37",
  "message": "Upload URL generated successfully"
}

Error Responses

{
  "success": false,
  "error": "Rate limit exceeded. Maximum 10 uploads per hour."
}

{
  "success": false,
  "error": "Invalid duration. Maximum 300 seconds allowed."
}

Upload Process

Request upload URL from this endpoint
Upload video file directly to the returned uploadURL using a POST request with form data
Monitor processing status using the Video Status endpoint
Use videoUID in token creation once processing is complete

Video Status

Check the processing status of an uploaded video.

GET /api/v1/video-status?uid={videoUID}

Query Parameters

Parameter

Type

Required

Description

uid

string

Yes

Video UID returned from upload endpoint

Response

{
  "success": true,
  "video": {
    "uid": "c0ee021fd95c4f0d8cc13c70c6172d37",
    "state": "nsfw_approved",
    "thumbnailUrl": "https://customer-xyz.cloudflarestream.com/.../thumbnail.jpg",
    "thumbnailIpfsHash": "QmXXXXXXXXX",
    "streamUrl": "https://customer-xyz.cloudflarestream.com/.../manifest/video.m3u8",
    "duration": 15.2,
    "width": 640,
    "height": 480,
    "size": 2097849,
    "created": "2025-06-27T08:31:13.023047Z"
  }
}

Video States

State

Description

uploading

Video is being uploaded to Cloudflare

processing

Video is being processed and encoded

nsfw_checking

Content moderation in progress

nsfw_approved

✅ Video approved and ready for use

nsfw_rejected

❌ Video rejected due to inappropriate content

error

Processing failed

When launching your token you can now include the additional videoUID value.

{
  "name": "MyMemeCoin",
  "symbol": "MMC",
  "description": "A memecoin with video content",
  "videoUID": "c0ee021fd95c4f0d8cc13c70c6172d37",
    ... other details
}

This will use an automatically generated image from your video. If you would like to customise the thumbnail used for the token you can use the Image Upload api and include the resulting IPFS hash in your token creation.

{
  "name": "MyMemeCoin",
  "symbol": "MMC",
  "description": "A memecoin with video content",
  "videoUID": "c0ee021fd95c4f0d8cc13c70c6172d37",
  "imageIpfs": "QmCustomImageHash",

}

List User Videos

Get all videos uploaded by a specific user.

POST /api/v1/video-status

Request Body

{
  "userId": "user123"
}

Response

{
  "success": true,
  "videos": [
    {
      "uid": "video1",
      "state": "nsfw_approved",
      "thumbnailIpfsHash": "QmXXXXXX",
      "created": "2025-06-27T08:31:13.023047Z"
    }
  ],
  "count": 1
}

Add video to your app

Enhanced Token Metadata

When a video is included, the token metadata structure is enhanced:

{
  "name": "MyMemeCoin",
  "description": "A memecoin with video content",
  "image": "ipfs://QmCustomImageHash",
  "animation_url": "https://customer-xyz.cloudflarestream.com/.../manifest/video.m3u8",
  "properties": {
    "websiteUrl": "",
    "discordUrl": "",
    "twitterUrl": "",
    "telegramUrl": ""
  },
  "video": {
    "uid": "c0ee021fd95c4f0d8cc13c70c6172d37",
    "duration": 15.2,
    "thumbnail": "https://customer-xyz.cloudflarestream.com/.../thumbnail.jpg",
    "streamUrl": "https://customer-xyz.cloudflarestream.com/.../manifest/video.m3u8",
    "width": 640,
    "height": 480,
    "size": 2097849,
    "created": "2025-06-27T08:31:13.023047Z"
  }
}

You can use the streamUrl and thumbnail in your app to showcase your videos.

Launch Token

POST /api/v1/{{ base | base-sepolia | robinhood }}/launch-memecoin

Tokens can be launched on base, base-sepolia or robinhood. See Supported Chains for what each one allows.

Creates a new memecoin token on the selected network with the following default parameters:

$10k starting market cap
80% dev / 20% community split
No revenue manager
Launched immediately; fair launch and sniper protection are currently paused

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

Value

name

Token name.

symbol

Token symbol (max 8 characters).

imageIpfs

IPFS hash from the image upload endpoint. Optional only if you supply an approved videoUID instead, in which case the video thumbnail is used.

description is optional and defaults to an empty string.

Creator Authentication Options (choose at most one)

Name

Value

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

Name

Value

sniperProtection

boolean : Currently paused. Must be omitted or false; sending true returns a 400. See Antibot Protection.

revenueManagerAddress

Ethereum address of a deployed revenue manager (must be valid address format)

feeSplitManagerAddress

Ethereum address of a deployed fee split manager (must be valid address format)

feeSplitRecipients

An array of Ethereum wallet addresses that will automatically receive an equal share of fees from the launched token [0x123..., 0xabc...]

creatorShare

Only include when specifying feeSplitRecipients if you also want the creator to take a portion of the fees. (default: 0, basis points so 8000 = 80%)

marketCap

Initial market cap in USDC (default: 10,000 = 10000000000)

creatorFeeSplit

Creator fee allocation in basis points (default: 8000 = 80%)

videoUID

UID of a video that has passed moderation. Attaches video metadata to the token and, when no imageIpfs is given, uses the video thumbnail as the image.

websiteUrl

Website URL

telegramUrl

Telegram group URL

discordUrl

Discord server URL

twitterUrl

Twitter/X URL

Rate Limits: Maximum 2 memecoin launches per minute per IP address

Antibot Protection

Currently paused. Sniper protection depends on fair launch, and both are temporarily disabled. Sending sniperProtection: true, or a non-zero fairLaunchSupply or fairLaunchDuration, is rejected with a 400 before the launch is queued:

{
  "success": false,
  "error": "Sniper protection has been temporarily paused (requires fair launch). Please omit this parameter or set to false."
}

Omit these fields, or send sniperProtection: false and "0" for the fair launch values. This page will be updated when they are re-enabled.

When active, sniperProtection caps any single wallet at 0.25% of total supply for the duration of the fair launch, then lifts the cap once fair launch ends.

Treasury Management Options for Token Launches

The memecoin launch API supports four distinct treasury management options:

No Treasury Management: Default behavior with no fee splitting
Revenue Manager: Use a pre-deployed revenue manager contract
Fee Split Manager: Use a pre-deployed fee split manager contract
Custom Fee Split: Define recipients directly in the launch request

Field Documentation

Name

Type

Description

revenueManagerAddress

string (optional)

Address of a pre-deployed revenue manager contract

feeSplitManagerAddress

string (optional)

Address of a pre-deployed fee split manager contract

feeSplitRecipients

Array (optional)

Array of fee split recipients in one of three formats (see below). Remember to also inclue creatorShare if you want the token creator to take a portion of the fees.

Mutual Exclusivity Rules

You can specify either revenueManagerAddress OR feeSplitManagerAddress, never both
You cannot specify manager addresses and feeSplitRecipients at the same time
Choose only one treasury management option per token

Enhanced feeSplitRecipients Field

The feeSplitRecipients field supports three formats:

1. Array of wallet addresses (legacy format)

"feeSplitRecipients": [
  "0x1234567890123456789012345678901234567890",
  "0xabcdefabcdefabcdefabcdefabcdefabcdefabcd"
]

2. Array of objects with account types (even split):json

"feeSplitRecipients": [
  {"type": "email", "id": "user@example.com"},
  {"type": "twitter", "id": "username"}, 
  {"type": "farcaster", "id": "username"},
  {"type": "wallet", "id": "0x1234567890123456789012345678901234567890"}
]

3. Array of objects with custom splits:json

"feeSplitRecipients": [
  {"type": "email", "id": "user@example.com", "split": "5000000"},
  {"type": "twitter", "id": "username", "split": "3000000"},
  {"type": "wallet", "id": "0x123...", "split": "2000000"}
]

Custom Split Rules

When using custom splits, all recipients must have splits if any recipient has a custom split
Splits must sum to exactly 10000000 (representing 100.00000%)
Split values are in micro-percentages: multiply UI percentage by 100000
Example: 33.33333% = "3333333", 50% = "5000000"
Maximum 100 recipients allowed
5 decimal precision supported

If you also want the creatorAddress to receive a portion of the fees you need to specify a creatorShare as part of the POST body. Omiitting the value defaults to a 0 share or the creator.

Account Type Validation

Type

Validation Rule

Example

wallet

Must be valid Ethereum address (0x + 40 hex chars)

"0x1234567890123456789012345678901234567890"

email

Must be valid email format

"user@example.com"

twitter

Alphanumeric + underscores, max 15 chars

"justinavery"

farcaster

Alphanumeric + underscores, 1+ chars

"javery"

Headers

Name

Value

Content-Type

application/json

Body

No Fee Management options

{
  "name": "Example Coin",
  "symbol": "EXCOIN",
  "description": "This is an example memecoin for demonstration purposes.",
  "imageIpfs": "QmR4Tnqvm4SahFwez3FBCbweYwUPUXo2SP8yePhLXYQJkd",
  "websiteUrl": "https://example.com",
  "discordUrl": "https://discord.gg/example",
  "twitterUrl": "https://twitter.com/example",
  "telegramUrl": "https://t.me/example",
  "creatorAddress": "0x498E93Bc04955fCBAC04BCF1a3BA792f01Dbaa96",
  "marketCap": "10000000000",
  "creatorFeeSplit": "8000",
}

Fee Split

{
  "name": "Community Coin",
  "symbol": "COMM",
  "description": "A token with shared revenue among community members",
  "imageIpfs": "QmX7UbPKJ7Drci3y6p6E8oi5TpUiG7NH3qSzcohPX9Xkvo",
  "websiteUrl": "https://community.example.com",
  "creatorAddress": "0x498E93Bc04955fCBAC04BCF1a3BA792f01Dbaa96",
  "creatorShare": 5000 // creator receives 50% of the fees, the other 50% shared to feeSplitRecipients
  // NEW: Fee Split Recipients (choose this OR revenueManagerAddress, not both)
  "feeSplitRecipients": [
    "0x1234567890123456789012345678901234567890",
    "0xabcdefabcdefabcdefabcdefabcdefabcdefabcd",
    "0x9876543210987654321098765432109876543210"
  ],
  
  // Optional advanced settings
  "marketCap": "10000000000",
  "creatorFeeSplit": "8000",
}

{
  "name": "Community Coin",
  "symbol": "COMM",
  "description": "A token with shared revenue among community members",
  "imageIpfs": "QmX7UbPKJ7Drci3y6p6E8oi5TpUiG7NH3qSzcohPX9Xkvo",
  "websiteUrl": "https://community.example.com",
  "creatorAddress": "0x498E93Bc04955fCBAC04BCF1a3BA792f01Dbaa96",
  "revenueManagerAddress": "0x57ac78c4a704233e274bbcdeb057ba640b65de23",
  // Optional advanced settings
  "marketCap": "10000000000",
  "creatorFeeSplit": "8000",
}

Option 1: No Treasury Management

{
  "name": "Simple Token",
  "symbol": "SIMPLE",
  "description": "A basic token with no fee management",
  "imageIpfs": "QmX7UbPKJ7Drci3y6p6E8oi5TpUiG7NH3qSzcohPX9Xkvo",
  "creatorAddress": "0x498E93Bc04955fCBAC04BCF1a3BA792f01Dbaa96"
}

Option 2: Revenue Manager (require Revenue Manager)

{
  "name": "Revenue Token",
  "symbol": "REV", 
  "description": "A token using a revenue manager",
  "imageIpfs": "QmX7UbPKJ7Drci3y6p6E8oi5TpUiG7NH3qSzcohPX9Xkvo",
  "creatorAddress": "0x498E93Bc04955fCBAC04BCF1a3BA792f01Dbaa96",
  "revenueManagerAddress": "0x712fa8ddc7347b4b6b029aa21710f365cd02d898"
}

Option 3: Fee Split Manager (require Fee Split Manager)

{
  "name": "Split Token",
  "symbol": "SPLIT",
  "description": "A token using a pre-deployed fee split manager", 
  "imageIpfs": "QmX7UbPKJ7Drci3y6p6E8oi5TpUiG7NH3qSzcohPX9Xkvo",
  "creatorAddress": "0x498E93Bc04955fCBAC04BCF1a3BA792f01Dbaa96",
  "feeSplitManagerAddress": "0xb31435D40c0cB02c27bf732940dB3d9e4A3b253A"
}

Which manager gets deployed. feeSplitRecipients deploys a fee split manager as part of the launch. On Base and Base Sepolia that is a static AddressFeeSplitManager; on Robinhood it is a DynamicAddressFeeSplitManager, whose recipient shares can be changed after deployment by the moderator (the resolved creator). The request and the response are the same either way — the deployed instance is returned as feeSplitManagerAddress on the status endpoint.

Option 4: Custom Fee Split (Even Distribution, no fees for the creator)

{
  "name": "Community Token",
  "symbol": "COMM",
  "description": "A token with shared revenue among community members",
  "imageIpfs": "QmX7UbPKJ7Drci3y6p6E8oi5TpUiG7NH3qSzcohPX9Xkvo",
  "creatorAddress": "0x498E93Bc04955fCBAC04BCF1a3BA792f01Dbaa96",
  "feeSplitRecipients": [
    {"type": "email", "id": "founder@example.com"},
    {"type": "twitter", "id": "justinavery"},
    {"type": "farcaster", "id": "javery"},
    {"type": "wallet", "id": "0x1234567890123456789012345678901234567890"}
  ]
}

Option 5: Custom Fee Split (Custom Percentages, 20% of the fees to the creator)

{
  "name": "Weighted Token", 
  "symbol": "WCOMM",
  "description": "A token with custom revenue splits",
  "imageIpfs": "QmX7UbPKJ7Drci3y6p6E8oi5TpUiG7NH3qSzcohPX9Xkvo",
  "creatorAddress": "0x498E93Bc04955fCBAC04BCF1a3BA792f01Dbaa96",
  "creatorShare": 2000
  "feeSplitRecipients": [
    {"type": "email", "id": "founder@example.com", "split": "5000000"},
    {"type": "twitter", "id": "justinavery", "split": "3000000"}, 
    {"type": "wallet", "id": "0x123...", "split": "2000000"}
  ]
}

Response

{
  "success": true,
  "message": "Memecoin launch request queued",
  "jobId": "40",
  
  // Queue status will show how long the expected flaunch time should be. The
  // `estimatedWaitSeconds` can offset the initial "Check Launch Status" delay.
  "queueStatus": {
    "position": 0,
    "waitingJobs": 0,
    "activeJobs": 1,
    "estimatedWaitSeconds": 0
  },
  
  // Privy data will vary depending on the `creatorType` specified
  "privy": {
    "type": "wallet",
    "address": "0x498E93Bc04955fCBAC04BCF1a3BA792f01Dbaa96"
  }
}

{
  "success": false,
  "error": "Missing required fields: name, symbol, description, imageIpfs"
}

{
  "success": false,
  "error": "Cannot specify both revenueManagerAddress and feeSplitRecipients. Choose only one treasury option."
}

{
  "success": false,
  "error": "Invalid fee split recipient address: 0xinvalidaddress"
}

{
  "success": false,
  "error": "Duplicate addresses found in fee split recipients"
}

Check Launch Status

GET /api/v1/launch-status/{{ jobId }}

Retrieves the launch status of a jobId. This endpoint is chainless — the job already knows which chain it was queued for.

Headers

Name

Value

Content-Type

application/json

Response

{
  "success": true,
  "state": "completed",
  "queuePosition": 0,
  "estimatedWaitTime": 0,
  "transactionHash": "0x04e594ee46312eecee8827aa2fef777dd2a94d247b723662be3a6daabb300028",
  "collectionToken": {
    "address": "0x06199b4b69f815141C197D034698d9E67Cdd265b",
    "imageIpfs": "QmQX8pdLRGeNps92Ma4esew7cbnYuBxQK7xUvp5soe3Lec",
    "name": "Community Coin",
    "symbol": "COMM",
    "tokenURI": "ipfs://QmSxzzNaeHbYZbPyFF29Z1PrhrsfNNMyFvebZeuLPrkzvA",
    "creator": "0x498E93Bc04955fCBAC04BCF1a3BA792f01Dbaa96"
  },
  "revenueManagerAddress": null,
  "feeSplitManagerAddress": "0x6baa4ec493a9698dc7388c0f290e29ea3d149f99",

  // Each entry carries the resolved wallet, its share, and the value you
  // originally supplied (an email or handle resolves to an address here).
  // `null` when the launch had no fee split.
  "feeSplitRecipients": [
    {
      "address": "0x1234567890123456789012345678901234567890",
      "percentage": "40.00000",
      "originalInput": "someone@example.com"
    },
    {
      "address": "0xabcdefabcdefabcdefabcdefabcdefabcdefabcd",
      "percentage": "60.00000",
      "originalInput": "0xabcdefabcdefabcdefabcdefabcdefabcdefabcd"
    }
  ]
}

{
  "success": true,
  "state": "waiting",
  "queuePosition": 2,
  "estimatedWaitTime": 120
}

{
  "success": true,
  "state": "active",
  "queuePosition": 0,
  "estimatedWaitTime": 0
}

{
  "success": true,
  "state": "failed",
  "queuePosition": 0,
  "estimatedWaitTime": 0,
  "transactionHash": null,
  "error": "Reason the launch failed",
  "collectionToken": null
}

If the transaction was already broadcast before the failure, the hash is preserved and the response is annotated. Check the block explorer before retrying — the launch may in fact have succeeded.

{
  "success": true,
  "state": "failed",
  "transactionHash": "0x04e594ee...",
  "transactionMayHaveSucceeded": true,
  "error": "<reason>. Note: Transaction was submitted (0x04e594ee...) - please check block explorer to verify status."
}

{
  "success": false,
  "error": "Job not found"
}

PreviousProtocol Fee Switch NextREST Data API

Last updated 15 days ago

Was this helpful?