Bundle & Sniper Wallets

Applies to type": "create_token" bodies. Each entry uses the same kind of encrypted API key as api_key (see How to get an API key).

Bundle mode

Multiple wallets buy in the same block as the create.

Supported platforms (typical server logic): pump, bonk, usd1, bags for bundle; sniper on overlapping sets — follow errors from the live server if a combo is unsupported.

bundle_wallets format

Each entry:

encrypted_api_key:buy_amount_in_sol

Example:

{
  "type": "create_token",
  "session_id": "<jwt>",
  "api_key": "<encrypted_creator>",
  "mode": "pump",
  "name": "Bundle Token",
  "ticker": "BUNDLE",
  "buy_amount": 1,
  "bundle": true,
  "bundle_wallets": "wallet1_key:0.5,wallet2_key:0.3,wallet3_key:0.2"
}

Sniper wallets

Buys run after the create lands; each entry can use its own delay.

Region note: the web client always POSTs sniper payloads to the NA-East deploy base (https://nyc.j7tracker.io/deploy), not the selected regional host.

Format

encrypted_api_key:buy_amount_in_sol:delay_ms

• delay_ms — 0 = ASAP after land; keep delays reasonable (e.g. ≤ 60000 ms for typical use).

Example:

{
  "type": "create_token",
  "session_id": "<jwt>",
  "api_key": "<encrypted_creator>",
  "mode": "pump",
  "name": "Sniped Token",
  "ticker": "SNIPE",
  "buy_amount": 1,
  "sniper_wallets": "wallet1_key:0.5:0,wallet2_key:0.3:500,wallet3_key:0.2:2000"
}

When sniper_wallets is set, execution may be coordinated similarly to bundle flows where supported.