Generic transactions

Every request is a JSON text frame with a top-level platform and type.

Request envelope

{
  "platform": "pump_fun",
  "type": "create_with_image_url"
}

Each platform page documents the rest of the payload for that method.

Shared request objects

`transaction_data`

Used by launch-style requests on pump_fun, raydium_launchpad, bags, heaven, liquid_af, four_meme, clanker_base, and nad_fun.

Field	Type	Notes
`rpcs`	`string[]`	Backend RPC lanes for the request. Use `astralane` as the recommended fast lane when available.
`identifier`	`string`	Your request id. This is the main correlation key in streamed responses.
`priority_fee`	`number`	Platform-specific fee field. On Solana flows this is a lamport priority fee.
`payer_wallet`	`string`	Wallet/address that signs and pays for the transaction.

Example:

{
  "transaction_data": {
    "rpcs": ["astralane"],
    "identifier": "req_123",
    "priority_fee": 1000000,
    "payer_wallet": "YOUR_WALLET"
  }
}

For latency-sensitive flows, astralane is the recommended RPC lane.

`launch_data`

Used by launch-style requests.

Field	Type	Notes
`name`	`string`	Token name.
`symbol`	`string`	Token symbol.
`description`	`string`	Empty string is allowed.
`twitter`	`string`	Usually the X/Twitter or source URL for the launch.
`attached_referral`	`string \| null`	Optional referral code/id.
`website`	`string \| null`	Optional website URL.
`generated`	`boolean`	Whether the launch metadata was AI-generated.
`multi_deploy_count`	`number`	Optional multi-launch count for supported launchpads.

`buy_config`

Shared by the Solana launch-style creators: pump_fun, raydium_launchpad, bags, heaven, and liquid_af. Standard:

{
  "type": "standard",
  "buy_amount": 50000000,
  "min_tokens_out": 0
}

Bundled:

{
  "type": "bundled",
  "buy_amount": 50000000,
  "min_tokens_out": 0,
  "bundles": [
    {
      "pubkey": "SNIPER_WALLET",
      "buy_amt": 20000000,
      "delay": 0
    }
  ]
}

`supply_transfer`

Some launchpads accept an optional supply transfer after launch. It can be sent as either a destination string or a structured object. String form:

"supply_transfer": "DESTINATION_WALLET"

Structured form:

{
  "supply_transfer": {
    "destination_wallet": "DESTINATION_WALLET",
    "percent_basis_points": 2500
  }
}

See TXResponses for the streamed response format, common msg_type values, and terminal-response handling.

Introduction

Dashboard

Features

Presets

Customization

Scrapist

API

Request envelope

Shared request objects

`transaction_data`

`launch_data`

`buy_config`

`supply_transfer`

​Request envelope

​Shared request objects

​transaction_data

​launch_data

​buy_config

​supply_transfer

Request envelope

Shared request objects

`transaction_data`

`launch_data`

`buy_config`

`supply_transfer`