# SlotShark API guide This is the complete SlotShark HTTP API in one document, written so a developer or an AI coding assistant can build on it without further help. It covers: - Connection: keys, base URLs, request and error conventions. - Wallets: create or import wallets, set them up to trade, withdraw SOL. - Solana trading: buy, sell, and exit orders attached to a buy. - Token API: move a token between your own wallets, and read market data and your holdings. - Automation configs: the routes they share, then each tab in the dashboard's order: Twitter Sniper, Copytrade, Callout Sniper (with FOMO Thesis mode), Deploy Sniper, PF Claims, Burn Sniper. Each saved config trades on its own from your wallet once enabled. The same configs show in the dashboard and the Telegram bot. This guide changes often. If you saved a copy more than a couple of days ago, fetch it again from `https://slotshark.xyz/dashboard/llms.txt` before you rely on it. ## Connection **Key.** Every request sends `Authorization: Bearer `. The key is shown in the dashboard's **Developer API** tab (`https://slotshark.xyz/dashboard?tab=devapi`). It expires 30 days after it was issued, and logging in again does not extend it. Rotating it there issues a new 30-day key and revokes every older key. It grants full trading access to your wallets, so keep it out of source code and logs, and never share it. **Body.** Requests with a body send JSON with `Content-Type: application/json`. **Base URLs.** | API | Base URL | |-----|----------| | US | `https://us.slotshark.xyz` | | EU | `https://eu.slotshark.xyz` | One key works on both. Pick one and use it for everything: configs saved on one are shared with the other, and a wallet's `taskAccountCount` is reported by the base URL you call. **Wallets.** Wallet addresses are base58 public keys. "Your wallets" or "your active wallets" means every wallet `GET /api/dashboard/wallets` lists. A wallet can trade once its `taskAccountCount` is above 0: set that up with `POST /api/dashboard/wallets//task-accounts` (Wallets part). **Amounts.** Amounts are decimal SOL and dollar filters are USD. Percentages are plain numbers: `25` means 25%. **Errors.** A refused request answers a non-2xx status with a JSON `error` string, often with a `field` naming the offending input and a stable `code`. Unless its section says otherwise, a refused request changes nothing and sends nothing. **Support.** For any problem or question, reach out to @pudgywizz on Telegram. **Rate limit.** Config writes (create, edit, delete, reset, and turning configs on or off) are limited to 100 per minute per account. Over the limit the API answers `429` with `"code": "rate_limited"`. Reads are not limited. **Use bulk requests.** To pause or start more than one config, always send one `bulk-enabled` request (PART 5), never one edit per config. Sending many edits one by one instead of a bulk request can get your account banned. Only re-save a config when something in it actually changed. ============================================================================== PART 2: Wallets ============================================================================== # Wallets API Create, import, fund and set up your trading wallets, and withdraw SOL from them. Same data as the dashboard's **Wallets** tab. ## Routes | Method | Path | Body | Returns | |--------|------|------|---------| | GET | `/api/dashboard/wallets` | none | `[ { "pubkey", "label", "taskAccountCount", "enabled", "feedEnabled" } ]` | | GET | `/api/dashboard/wallets//balance` | none | `{ "pubkey", "balanceSol", "balanceLamports" }` | | POST | `/api/dashboard/wallets/create` | `{ "label"? }` | `{ "pubkey", "secretKey" }` | | POST | `/api/dashboard/wallets/import` | `{ "secretKey", "label"? }` | `{ "pubkey" }` | | POST | `/api/dashboard/wallets//task-accounts` | `{ "count" }` | `{ "pubkey", "taskAccountCount" }` | | POST | `/api/dashboard/wallets//label` | `{ "label" }` | `{ "pubkey", "label" }` (the label as sent; the list shows it trimmed) | | POST | `/api/dashboard/wallets//enable` | `{ "enabled": true \| false }` | `{ "pubkey", "enabled" }` | | POST | `/api/dashboard/wallets//feed` | `{ "enabled": true \| false }` | `{ "pubkey", "feedEnabled" }` | | GET | `/api/dashboard/wallets//usage` | none | `{ "total", "enabled", "byStore" }` | | POST | `/api/dashboard/wallets//replace` | `{ "newWalletPubkey" }` | `{ "replaced", "total" }` | | POST | `/api/dashboard/wallets/withdraw` | `{ "wallet", "destination", "amountSol" }` | `{ "id", "expiresAt" }` | | POST | `/api/dashboard/wallets/withdraw//confirm` | `{ "code" }` | `{ "signature" }` | | DELETE | `/api/dashboard/wallets/` | none | `{ "success": true }` | A `` that is not one of your wallets is refused with `403` (`not your wallet`, or `wallet-not-yours` on usage and replace). ## Setting up a new wallet 1. `POST /api/dashboard/wallets/create` (or `import` an existing secret key). 2. Fund it with at least 0.05 SOL: send SOL to its `pubkey`, or withdraw from another of your wallets to it. 3. `POST /api/dashboard/wallets//task-accounts` with `{ "count": 4 }`. 4. Check `GET /api/dashboard/wallets`: `taskAccountCount` above 0 and `enabled` true. If `enabled` is false, `POST /api/dashboard/wallets//enable` with `{ "enabled": true }`. ## Fields | Field | Meaning | |-------|---------| | `label` | At most 12 characters, unique among your wallets (case ignored). Optional on create and import; required on the label route. | | `secretKey` | Base58, 64 bytes. On `create` it is returned only in that response, so save it. | | `taskAccountCount` | Each task account carries one pending trade at a time, so more let more trades run at once. 4 is the standard setup. A wallet with `0` cannot trade, and enabled configs cannot use it. | | `count` | Task accounts to add, `1` to `20`. They cost about 0.0075 SOL each, paid from the wallet over about 2 minutes: 4 cost about 0.03 SOL. Reaching 4 on a wallet that was never enabled also sets `enabled` to true. | | `enabled` | Whether the Telegram bot trades from the wallet. A wallet trades through this API while it is switched on anywhere (`enabled`, the Chrome extension or the Twitter Tracker), an enabled config uses it, or it has open exit orders. Turning it on tops the wallet up to 4 task accounts if it has fewer. | | `feedEnabled` | Whether the wallet is listed in the dashboard's Twitter Tracker. Needs task accounts. | | `byStore` | Your configs naming the wallet per tab, paused included: `copytrade`, `sniper`, `claimSniper`, `burnSniper`, `calloutSniper`, `twitter`. | You can hold up to 50 wallets. `task-accounts` takes a second or two per account. If it times out or answers `Task account setup did not finish`, read `taskAccountCount` before calling again: the accounts may still be on their way. ## Withdraw Two steps, on the same base URL. `POST /api/dashboard/wallets/withdraw` records the request, sends an 8-digit code to your Telegram, and returns an `id`. `POST /api/dashboard/wallets/withdraw//confirm` with `{ "code": "" }` sends it, within 1 hour of the first step. `code` is a string of 8 digits, leading zeros included (a JSON number counts as a wrong code). The answer's `signature` means sent, not landed. A missing or wrong code keeps the `id` usable (a wrong one counts, and the 5th cancels the withdrawal), unless the wallet is paused (`withdraw_code_cooldown`); any other refused confirm uses up the `id`: start again with a new withdraw. A new withdraw of a wallet replaces your earlier one of that wallet still waiting for its code. Refusals are `400` with a `code`: - `withdraw_code_required`: the confirm carried no code. - `withdraw_code_invalid`: the code is wrong; try again. - `withdraw_code_locked`: the 5th wrong code; the withdrawal is cancelled. - `withdraw_request_again`: this withdrawal can no longer be confirmed; request it again. - `withdraw_no_telegram`: no Telegram account to send the code to (first step). - `withdraw_too_many_pending`: 5 withdrawals are already waiting for this wallet (first step). - `withdraw_code_cooldown`: 10 wrong codes on this wallet in the last 24 hours; withdrawals from it are paused until fewer than 10 fall in that window, at most 24 hours (either step). - `destination` is any Solana address other than the wallet itself. - `amountSol` is decimal SOL. The wallet must keep at least 0.00089088 SOL after the amount and the 0.000005 SOL fee. An amount that is not positive, rounds to 0 lamports, or is above 1,000,000,000 SOL is refused. ## Replace `POST /api/dashboard/wallets//replace` moves every one of your configs that names `` (paused included) to `newWalletPubkey`. The new wallet must be yours and have task accounts. Open positions and exit orders stay on the old wallet. At most 30 per minute. | Error | Meaning | |-------|---------| | `403 wallet-not-yours` | `` or the new wallet is not yours. | | `400 same-wallet` | Both are the same wallet. | | `409 wallet-not-ready` | The new wallet has no task accounts. | | `400 bad-request` | `newWalletPubkey` missing or not an address. | | `429 rate_limited` | Over 30 a minute. | | `500 partial` | Some configs moved (`replaced`, `total`): send it again. | | `503` | Try again in a moment. | ## Delete `DELETE /api/dashboard/wallets/` is refused with `409` while any of your configs names the wallet, paused ones included (the error counts them as tasks): replace or delete them first. Withdraw what you want to keep before deleting. The SOL paid for task accounts is not returned. Keep the secret key if you may need the wallet again. ## Errors A refused request answers a non-2xx status with a JSON `error` string. ============================================================================== PART 3: Solana trading ============================================================================== # Solana Trading API Buy and sell tokens from your SlotShark wallets, and attach exit orders to a buy. ## POST /buy ```jsonc { "mint": "", // REQUIRED. A pool address works too "solAmount": 0.5, // REQUIRED. SOL to spend, > 0 "wallet": "",// REQUIRED. One of your wallets (case-sensitive) "slippage": 25, // optional, %, default 25 "tip": 0.005, // optional, SOL, omit = automatic "priorityFee": 0.003, // optional, SOL, omit = automatic "antimev": false, // optional, default false "skipIfBought": false, // optional "skipIfHeld": false, // optional "minLiquidity": 3000, // optional, USD "minMarketCap": 5000, // optional, USD "maxMarketCap": 500000, // optional, USD "minTokenAgeSecs": 0, // optional "maxTokenAgeSecs": 3600, // optional "maxPoolTax": 10, // optional, % "skipSusPools": false, // optional "allowedPlatforms": ["pumpfun"], // optional, omit = all platforms allowed, we recommend allowing all "retries": true, // optional "limitSells": [] // optional, see Limit orders } ``` | Field | Notes | |---|---| | `slippage` | How far the price may move against you, in percent, `0` or more. `100` accepts the price doubling. | | `tip` / `priorityFee` | In SOL. Omit for the automatic values. The tip is paid only when the swap succeeds; the priority fee is paid whenever the transaction lands, even if the swap fails. | | `skipIfBought` | Skip the buy when this wallet has already bought this token in the last 90 days. It stays skipped after you sell. | | `skipIfHeld` | Skip the buy while this wallet still holds the token, and allow it again after a full exit (5% or less left counts as exited). | | `minLiquidity` / `minMarketCap` / `maxMarketCap` | Pool filters in USD. Market cap is fully diluted (price x total supply). | | `minTokenAgeSecs` / `maxTokenAgeSecs` | Token age band in seconds. `min` = older than, `max` = fresher than. | | `maxPoolTax` | Refuse the buy when the pool's current swap tax is above this percent. | | `skipSusPools` | Refuse the buy when the pool trips the suspicious-pool checks. It can also flag a legitimate pool, most often a very fresh launch. | | `allowedPlatforms` | Buy only when the token trades on one of these: `pumpfun`, `raydium`, `meteora`, `moonshot`, `stonkfun`, `mayhem`, `pumpCustomPairs`, `embercurve`, `orca`. Omit to allow all. An empty list or an unknown id is refused. | | `retries` | If the token's bonding curve graduates while the buy is in flight, retry once on the new pool, never above your original price limit. | ### Response ```jsonc { "success": true, "signature": "", "error": null } // sent { "success": false, "error": "" } // refused or failed ``` `signature` means the transaction was sent, not that it landed. Do not rely on it to confirm the trade: the trade usually lands under a different signature. Check the wallet's balance of the token with `GET /token//info` instead. A refused buy sent nothing. Unknown or malformed values are a `400` with an `error` naming the problem. ## POST /sell ```jsonc { "mint": "", // REQUIRED. A pool address works too "sellPercent": 100, // REQUIRED. 1-100 of this wallet's balance, fractions allowed "wallet": "",// REQUIRED "slippage": 25, // optional, %, default 25 "tip": 0.005, // optional, SOL, omit = automatic "priorityFee": 0.003, // optional, SOL, omit = automatic "antimev": true, // optional, default true "retries": true // optional, retry once on the new pool if the token graduates } ``` The response has the same shape as `/buy`. A missing `sellPercent` is a `400` (`sellPercent is required (1-100)`). ## Limit orders Attach exit orders to a buy with `limitSells` (up to 50). Each order belongs to that buy, runs on its own, and fires at most once. ```jsonc { "mint": "", "solAmount": 1.0, "wallet": "", "limitSells": [ { "type": "time", "value": 30, "sellPercent": 50, "tip": 0.005, "priorityFee": 0.003 }, { "type": "pnl", "value": 100, "sellPercent": 25 }, { "type": "pnl", "value": -50, "sellPercent": 100 }, { "type": "trailing", "value": 5, "activatePct": 20, "sellPercent": 100 }, { "type": "mcap", "value": 1000000, "sellPercent": 50 }, { "type": "migration", "sellPercent": 100, "retries": true } ] } ``` Manual buys use the same rung types as automation configs. Each `type`'s `value`, `sellPercent`, the per-rung `tip`, `priorityFee`, `slippage`, `antimev` and `retries`, and the 3-day expiry work as in PART 5 (Exit rungs); a rung retries only when it sets `retries: true`. A `trailing` rung with `activatePct` 0 (the default) trails from your entry, so it also works as a stop loss until the price rises. ## Example ```bash curl -X POST https://us.slotshark.xyz/buy \ -H "Content-Type: application/json" \ -H "Authorization: Bearer YOUR_KEY" \ -d '{ "mint": "", "solAmount": 0.5, "wallet": "" }' ``` ============================================================================== PART 4: Token API ============================================================================== # Token API Move one token between wallets you already own, and read what you hold of it. Three endpoints: | | | |---|---| | `POST /wallet/token/split` | split one wallet's bag out across several of your wallets | | `POST /wallet/token/consolidate` | consolidate one token from several of your wallets into one | | `GET /token//info` | market data plus your per-wallet holdings and PnL for one token | The two move endpoints are plain transfers between wallets you own. They are not swaps: no pool is touched, no slippage applies, no fee is charged and the token amount is preserved. ## Every wallet in a request must be yours Both ends of every leg must be one of your own wallets. There is no free-text destination: an address that is not yours is refused with `Not your wallet:
` and nothing is sent. --- # POST /wallet/token/split One source wallet, up to 10 destinations, sent as a **single transaction**. Either the whole split lands or none of it does. ```jsonc { "mint": "", "from": "", "to": [ { "wallet": "", "pct": 40 }, { "wallet": "", "pct": 35 }, { "wallet": "", "pct": 25 } ] } ``` `pct` is a percentage of the source's current on-chain balance. Greater than 0, at most 100, at most two decimal places (`33.33` is fine, `33.333` is refused). The percentages for one source may total less than 100, in which case the remainder stays put, but never more. Each leg is floored to the token's smallest unit and the rounding remainder stays in the source, so a split can never draw more than the wallet holds. **Ten destinations is a hard cap**, because the whole split must fit in one transaction. Use two requests if you need more. # POST /wallet/token/consolidate Several sources, one destination, sent as **one transaction per source**. Each source signs and pays its own fee, so one source failing does not stop the others. ```jsonc { "mint": "", "to": "", "from": [ { "wallet": "", "pct": 100 }, { "wallet": "", "pct": 100 } ] } ``` Each source's percentages are capped at 100% of that source's own balance. There is no ten-wallet cap here, since sources do not share a transaction. ## Response Both endpoints return `200` with one row per requested leg: ```jsonc { "success": true, // true if at least one leg actually broadcast "warnings": [], // non-blocking notes about the token "legs": [ { "from": "", "to": "", "amount": "4000000", // raw token units sent "expectedReceived": "4000000", // differs only on a fee-bearing token "signature": "" // present when this leg broadcast }, { "from": "", "to": "", "amount": "0", "expectedReceived": "0", "error": "Source holds no balance for this token, nothing to move" } ] } ``` A leg carries either a `signature` or an `error`, never both. `success` is `true` when at least one leg broadcast, so check the legs, not just the top-level flag. ## What gets refused Refusals come back as `200` with `"success": false` and an `error` string. Refusals decided after your wallets are read also carry empty `warnings` and `legs` arrays; the earlier ones (rate limit, malformed body, a wallet outside your scope) carry only `success` and `error`. Nothing is signed or sent when a request is refused. A missing, invalid or expired key is a `401`. ## Live orders keep working Stop-losses and timed sells on a source wallet apply to whatever the wallet holds when they fire, so a partial move leaves them in place. Move 60% out of a wallet holding a stop-loss and the stop-loss guards the remaining 40%. A move that empties the wallet cancels its orders for that token, the same as a 100% sell. --- # GET /token/{mint}/info Market data for a mint plus what you hold of it, per wallet. ``` GET /token//info GET /token//info?wallet= ``` `` may also be a **pool address**: it resolves to the mint, so an address copied out of an Axiom URL works. `?wallet=` narrows the response to one of your wallets; an address outside your scope is refused rather than returning an empty list. ```jsonc { "success": true, "mint": "", "market": { "priceSol": 0.002, // per WHOLE token "priceUsd": 0.4, "mcapUsd": 400000000, "liquidityUsd": 50000, "totalSupply": "1000000000000000", // raw units, string "totalSupplyUi": 1000000000, "supplyIsEstimated": false, "decimals": 6, "ammType": "pump_swap", "poolFeePercent": null, // the pool's fee %, when reported "note": "..." }, "wallets": [ { "wallet": "", "label": "main", "balanceRaw": "1550000000", "balanceUi": 1550.0, "frozen": false, "bought": 2.0, // lifetime SOL spent on this mint in this wallet "sold": 0.5, // lifetime SOL received "holding": 3.1, // current bag at live price "realized": -1.5, // sold - bought "total": 1.6 // sold + holding - bought } ], "totals": { "bought": 2.0, "sold": 0.5, "holding": 3.1, "realized": -1.5, "total": 1.6 }, "walletsOmitted": 0 } ``` All figures are SOL unless the name ends in `Usd`. ## Things worth knowing before you trust the numbers **Only wallets ready to trade on this base URL are included.** Any other wallet of yours is skipped and counted in `walletsOmitted`. If that number is not zero, you are seeing a partial picture: enable the wallet (`POST /api/dashboard/wallets//enable` with `{ "enabled": true }`) to include it. `bought` and `sold` are fee-inclusive cash flows: a buy includes the platform fee, tip and priority fee; a sell is net of them. History for a position with no trade in 30 days and a holding worth under $1 is dropped, so a very old bag can show a balance with no purchase history. Tokens moved with split or consolidate keep their cost on the source wallet: after a move the source shows the whole `bought` on a smaller holding and the destination shows a holding with `bought` 0. Compare `totals` rather than single wallets after a move. --- ## Examples ```bash BASE=https://eu.slotshark.xyz KEY=your-bearer-key MINT= # What do I hold of this token, and what is it worth? curl -s "$BASE/token/$MINT/info" -H "Authorization: Bearer $KEY" # Just one wallet curl -s "$BASE/token/$MINT/info?wallet=" -H "Authorization: Bearer $KEY" # Split a bag 40/35/25 across three of your wallets curl -s -X POST "$BASE/wallet/token/split" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \ -d '{ "mint": "'"$MINT"'", "from": "", "to": [ { "wallet": "", "pct": 40 }, { "wallet": "", "pct": 35 }, { "wallet": "", "pct": 25 } ] }' # Move half out of one wallet, leaving the rest curl -s -X POST "$BASE/wallet/token/split" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \ -d '{ "mint": "'"$MINT"'", "from": "", "to": [ { "wallet": "", "pct": 50 } ] }' # Gather everything back into one wallet curl -s -X POST "$BASE/wallet/token/consolidate" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \ -d '{ "mint": "'"$MINT"'", "to": "", "from": [ { "wallet": "", "pct": 100 }, { "wallet": "", "pct": 100 } ] }' ``` ============================================================================== PART 5: Automation: shared routes ============================================================================== # Automation config routes Every automation tab uses the same routes. `` is one of `twitter`, `copytrade`, `calloutsniper`, `sniper`, `claimsniper`, `burnsniper`. | Method | Path | Body | Result | |---|---|---|---| | GET | `/api/dashboard//configs` | none | `200 { "configs": [ ... ] }` | | GET | `/api/dashboard//configs/` | none | `200` the config, no envelope (not on `twitter`) | | POST | `/api/dashboard//configs` | full config | `201 { "config": { ... } }` | | PUT | `/api/dashboard//configs/` | **full** config | `200 { "config": { ... } }` | | PATCH | `/api/dashboard//configs/` | **partial** config | `200 { "config": { ... } }` | | DELETE | `/api/dashboard//configs/` | none | `200 { "deletedAt": ... }` | | POST | `/api/dashboard//configs//reset` | none | `200 { "config": { ... } }`, resets the fire count | | POST | `/api/dashboard//configs/bulk-enabled` | `{ "enabled": true\|false, "configIds"?: [...] }` | `200 { "enabled", "updated", "unchanged", "failed" }` | `` is the `configId` from the list. Fetch the list, pick the config by its `name`, and use its id. An id that does not exist or is not yours returns `404`. **Wallet.** A config's wallet must be one of yours (`GET /api/dashboard/wallets`, PART 2). Creating or enabling a config on a wallet whose `taskAccountCount` is `0` returns `400` naming the wallet field. ## Rules every config body follows **Fees and filters go inside `snipeParams`.** Buy size and the trigger are top-level; fees, slippage, coin filters, the skip switches and `limitSells` live inside `snipeParams`. **Unknown keys are refused.** A key the tab does not take, at any depth, is a `400` naming it, with a hint when it is only in the wrong place: ```bash curl -X PATCH "https://eu.slotshark.xyz/api/dashboard/copytrade/configs/$ID" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \ -d '{ "tip": 0.02 }' # -> 400 unknown field "tip" (did you mean "snipeParams.tip"?) # send { "snipeParams": { "tip": 0.02 } } instead ``` **Errors.** A refused write is a `400` with an `error` message and, when it is about one field, that `field`. Only the first problem is reported. **PATCH and PUT.** `PATCH` merges your body over the stored config: nested objects (`snipeParams`, and on Twitter `params` and `taskTiming`) merge key by key, arrays (`limitSells`, watch lists, `allowedPlatforms`) are replaced whole, so send them complete. `PUT` replaces the whole config: a key you leave out goes back to its default. **Server-managed fields.** `configId`, `ownerTgChatId`, `originatingRegion`, `snipeCount`, `snipeCountBaseline`, `createdAt`, `updatedAt` and every `*UpdatedAt` are set by the server. A body may carry them (a config read back and sent as a `PUT` works); their values are ignored. List rows also carry a read-only `snipeRefunds`. **Fire count.** `maxSnipes` (Twitter: `maxBuyCount`) caps how many times a config fires. The count it is checked against is `snipeCount - snipeCountBaseline - snipeRefunds` (`snipeRefunds` are fires refused before anything was sent); the dashboard shows the same number. A cap below the current count is a `400`. `POST /configs//reset` sets the count back to 0. **Legacy fields.** A field marked legacy is still accepted for now but will stop being supported soon. If you use one, switch to the field named next to it. ## `snipeParams` reference Each tab lists which of these keys it takes; any other key is refused. | Field | Type | Notes | |---|---|---| | `slippage` | number (%) | Buy slippage. | | `tip` / `priorityFee` | number (SOL) | Buy tip and priority fee. Omit for the automatic values. | | `antimev` | boolean | Anti-MEV on the buy. Off unless set. | | `retries` | boolean | Retry once on the new pool if the coin's bonding curve graduates while the buy is in flight. | | `skipIfBought` | boolean | Skip when this wallet bought the coin in the last 90 days. Stays skipped after you sell. Per wallet and coin. | | `skipIfHeld` | boolean | Skip while this wallet holds the coin; allowed again after a full exit (5% or less left). Per wallet and coin. | | `skipSusPools` | boolean | Refuse pools that trip the suspicious-pool checks. It can also flag a legitimate pool, most often a very fresh launch. | | `safeSlippage` | boolean | Frontrun protection. | | `maxPoolTax` | number (%) | Refuse pools whose swap fee is above this. Omit for no cap; `0` is refused. | | `minMarketCap` / `maxMarketCap` | number (USD) | Fully diluted market cap at buy time. Omit for no bound; `maxMarketCap: 0` is refused. Unreadable data refuses the buy. | | `minLiquidity` | number (USD) | Minimum pool liquidity. | | `minTokenAgeSecs` / `maxTokenAgeSecs` | number (s) | `min` = older than, `max` = fresher than. An unknown age fails `max` and passes `min`. | | `migrationBuffer` | integer (bps) | 0 to 5000. How far below graduation a buy on a bonding curve is capped. | | `pileupBufferBps` | integer (bps) | 0 to 10000. | | `maxPoolFeeBps` | integer (bps) | Legacy. Still accepted, will stop being supported soon; use `maxPoolTax` instead. | | `limitSells` | array | Exit rungs, below. | Values must have the right type: numbers 0 or higher, booleans `true` or `false`, the bps fields whole numbers. Anything else is a `400`. ## Exit rungs (`limitSells`) Each config buy gets its own set of rungs, at most 50, fired at most once each. ```jsonc "limitSells": [ { "type": "pnl", "sellPercent": 50, "value": 100 }, // +100% PnL { "type": "pnl", "sellPercent": 100, "value": -50 }, // stop loss at -50% { "type": "trailing", "sellPercent": 100, "value": 20, "activatePct": 50 }, // trail 20% once +50% { "type": "mcap", "sellPercent": 50, "value": 1000000 }, // market cap >= $1M { "type": "time", "sellPercent": 100, "value": 300 }, // 300 s after the buy { "type": "migration", "sellPercent": 100 } // when the curve graduates ] ``` | `type` | `value` | |---|---| | `time` | Seconds after the buy, above 0. | | `pnl` | PnL percent. Negative is a stop loss. | | `trailing` | Drop from the peak in percent, above 0 and at most 100. `activatePct` is the PnL percent at which the trail starts (default 0, from the buy). | | `mcap` | Market cap in USD, fully diluted, not 0. Positive sells at or above it, negative at or below its absolute value. A target already met when the buy lands sells at once. | | `migration` | No `value`. Sells when the coin's bonding curve graduates. | `sellPercent` (1-100) is the share of the wallet's balance the rung sells. A rung may set its own `tip`, `priorityFee`, `slippage`, `antimev` and `retries`; omitted, it uses the automatic sell values with anti-MEV on. `pnl`, `trailing`, `mcap` and `migration` rungs expire unfired 3 days after the buy; `time` rungs do not. All remaining rungs for a coin stop once the wallet holds none of it. ## Platform ids (`allowedPlatforms`) | Id | Covers | |----|--------| | `pumpfun` | Pump Classic, PumpSwap | | `raydium` | Raydium AMM V4, CpSwap, CLMM, LaunchLab | | `meteora` | Meteora CPAMM (DAMM v2), DLMM, Dynamic Bonding Curve | | `moonshot` | Moonit | | `stonkfun` | StonkFun launches | | `mayhem` | Pump.fun Mayhem coins | | `pumpCustomPairs` | Pump.fun coins quoted in another token (neither SOL nor USDC) | | `embercurve` | EmberCurve launches | | `orca` | Orca Whirlpool | Omit the field to allow every platform, including ones added later (recommended). A list must name at least one id; `[]`, `null` and unknown ids are refused. A StonkFun, EmberCurve or custom-pair coin is allowed only by its own id. For Bags coins, `meteora` needs to be selected. ## Pause or start many configs at once Always send one `bulk-enabled` request instead of a `PATCH` per config. Many edits one by one instead of a bulk request can get your account banned. ```bash # pause every config you own on the tab curl -s -X POST "https://eu.slotshark.xyz/api/dashboard/copytrade/configs/bulk-enabled" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \ -d '{ "enabled": false }' # start only these three curl -s -X POST "https://eu.slotshark.xyz/api/dashboard/copytrade/configs/bulk-enabled" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \ -d '{ "enabled": true, "configIds": ["", "", ""] }' ``` - `enabled` (required): `true` to start, `false` to pause. - `configIds` (optional): up to 10000 ids. Omit it to apply to every config you own on that tab. Duplicates are ignored. - Each config that changes gets the checks a `PATCH { "enabled": ... }` would run, and a failure affects only that config. - Configs already in the requested state are reported as `unchanged` and not re-checked. The response is `200` even when some configs failed, so read `failed`: each entry is `{ "configId", "error", "field"? }`. Only a malformed body is a `400`. It counts as one write against the rate limit. ============================================================================== PART 6: Automation: Twitter Sniper ============================================================================== # Twitter Sniper API Create, update, and delete Twitter sniper configs over HTTP. A config watches one or more X/Twitter handles and auto-fires a buy (or a sell) the moment they do something you picked: post a contract address, tweet, engage with a tweet, follow somebody, change their bio or display name, or change their profile picture. This is the same data the dashboard's **Twitter** tab reads and writes, so a change made here shows up there immediately. ## The five modes `modeType` picks the trigger. It cannot be changed after a config is created: to switch a config to another mode, delete it and create a new one. | `modeType` | Dashboard label | Fires when | Which token gets traded | |---|---|---|---| | `ca_scanner` | CA scanner | a watched handle posts a tweet containing a contract address | whatever mint the tweet contains | | `mention` | New Tweet | a watched handle tweets, retweets, replies, quotes, updates their bio, or changes their display name | a fixed mint you pick up front | | `engagement` | Engagement | a watched handle replies to / retweets / quotes one of the tweets you list (or any tweet by the handles you list) | a fixed mint you pick up front | | `follow_unfollow` | Follow / Unfollow | a watched handle follows or unfollows another watched handle | a fixed mint you pick up front | | `pfp_update` | PFP update | a watched handle changes their profile picture | a fixed mint you pick up front | `ca_scanner` is the only mode that discovers the mint at fire time. Every other mode needs `params.tokenAddress` set when you create the config. ## The config object Every mode shares the same outer shell and differs only in `params`. ```jsonc { // ── identity ── "name": "elon watch", // 1-40 chars. REQUIRED "enabled": true, // REQUIRED "modeType": "mention", // one of the five above. REQUIRED, cannot change later "walletPubkey": "", // which of your wallets trades. REQUIRED // ── mode-specific trigger ── "params": { /* see the per-mode reference below */ }, // REQUIRED // ── optional bounds ── "maxBuyCount": 5, // cap on buys (whole number >= 1). Omit = unlimited "taskTiming": { "startMs": 1754600000000, "endMs": 1754700000000 }, // active window, epoch ms "allowedPlatforms": ["pumpfun","raydium"], // buy-venue filter. Omit = all venues // ── fees / slippage / exits (NESTED) ── "snipeParams": { "solAmount": 0.05, // buy size for CA scanner only (see note below) "slippage": 50, "limitSells": [ { "type": "pnl", "sellPercent": 50, "value": 100 }, { "type": "time", "sellPercent": 100, "value": 300 } ] } } ``` ### Field reference | Field | Type | Notes | |---|---|---| | `name` | string | 1-40 chars. Must be unique among your configs **of the same mode**, so a `mention` and a `pfp_update` config may share a name. | | `enabled` | boolean | Required on create and on a `PUT`; a `PATCH` keeps the stored value unless you send it. Set `false` to pause without deleting. | | `modeType` | enum | `ca_scanner` \| `engagement` \| `mention` \| `follow_unfollow` \| `pfp_update`. Cannot be changed after create. | | `walletPubkey` | base58 | Must be one of your own active wallets. A disabled config may keep the wallet it already has after that wallet leaves your active list (so you can still rename or tune it); setting a different wallet, or enabling the config, needs an active one. | | `maxBuyCount` | integer >= 1 | Whole number from 1 to 4294967295. Cap on buys: only buys count toward it. One cap covers the whole config, every handle and tweet id it lists. Once it is reached the config stops firing altogether, sells included (a config in sell mode, or a `follow_unfollow` sell on unfollow). Limit-sells already set on earlier buys keep working. Setting it to exactly the current count means "stop here". Omit for unlimited. | | `taskTiming` | object | `{ startMs, endMs }` in epoch milliseconds, each a whole number. Outside the window the config does not fire. Either bound may be omitted; with both set, `endMs` must be after `startMs`. | | `allowedPlatforms` | string[] | Platform ids in PART 5. Filters **buys only**; sells always fire. Omit the field to allow all venues. | | `params` | object | Mode-specific, see below. | | `snipeParams` | object | Fees, slippage, filters, limit-sells. | ### Server-managed fields The server also sets `disabledReason` when it switched a config off because its handles are no longer available for tracking. It clears the next time you enable the config. ### `snipeParams` Takes `solAmount`, `slippage`, `tip`, `priorityFee`, `antimev`, `retries`, `skipIfBought`, `skipIfHeld`, `skipSusPools`, `safeSlippage`, `maxPoolTax`, `minMarketCap`, `maxMarketCap`, `minLiquidity`, `minTokenAgeSecs`, `maxTokenAgeSecs`, `migrationBuffer`, `pileupBufferBps`, `limitSells`, `sellSlippage`, `sellTip`, `sellPriorityFee`, `sellAntimev`. Shared keys and exit rungs are in PART 5. Twitter-specific: | Field | Type | Notes | |---|---|---| | `solAmount` | number (SOL) | Buy size for **CA scanner**. The other four modes size the trade with `params.amount` and ignore this. | | `tip` / `priorityFee` | number (SOL) | `0` is not auto: a `0` tip sends the minimum tip and a `0` priority fee sends none. | | `sellSlippage` / `sellTip` / `sellPriorityFee` | number | Sell-side overrides, used when the config sells. Omit to reuse the buy-side value. The dashboard shows them for `follow_unfollow` and for configs in sell mode. | | `sellAntimev` | boolean | Sell anti-MEV; falls back to `antimev` when unset. | | `safeSlippage` / `migrationBuffer` | advanced | No control for them in the dashboard form. Leave them alone unless you know you want them. | | `pileupBufferBps` | number | Accepted (0 or more) but has no effect on a Twitter config. | An `mcap` rung waits while the market cap cannot be read. > **CA scanner: always send `snipeParams.solAmount`.** It sizes the buy and has no > default: creating a `ca_scanner` config without a `solAmount` greater than 0 is a `400`. ## Per-mode `params` ### `ca_scanner` (CA scanner) Watches up to 50 handles and buys any contract address they post. ```jsonc "params": { "targetHandles": ["alice", "bob"], // 1-50 handles. REQUIRED "triggers": { // at least mainTweet OR retweet must be true "mainTweet": true, // REQUIRED, true or false "retweet": false, // REQUIRED, true or false "quote": false, // optional "reply": false // optional }, "firstBuyOnly": false, // optional: buy a coin only the first time a handle posts it "keywordsInclude": ["presale", "launching"], // optional, OR-matched, whole words, max 50 entries, 64 chars each "keywordsExclude": ["rug", "scam"], // optional, whole words, any hit skips the tweet "keywordsIncludeSubtweetDepth": 1, // optional, 0-8, default 1 (see Keyword scan depth) "keywordsExcludeSubtweetDepth": 1 } ``` Buy size comes from `snipeParams.solAmount`. ### `mention` (New Tweet) Fires on activity from any of up to 50 handles and buys or sells a mint you pre-pick. ```jsonc "params": { "targetHandles": ["alice", "bob"], // 1-50 handles. REQUIRED unless targetHandle is sent // "targetHandle": "alice", // or watch one handle. When targetHandles is sent it // wins, and targetHandle is set to its first entry. // Duplicates are dropped. "targetTriggers": { // at least one must be true "tweet": true, "retweet": false, "bioUpdate": false, // REQUIRED, true or false "reply": false, "quote": false, "nameUpdate": false // optional }, "keywordsInclude": ["alpha"], // optional, whole words (empty = match any tweet text) "keywordsExclude": ["scam"], // optional, whole words "keywordsIncludeSubtweetDepth": 0, // optional, 0-8, default 0 "keywordsExcludeSubtweetDepth": 0, "tokenAddress": "", // REQUIRED "amount": 0.1 // buy 0.1 SOL ... OR ... // "sellPercent": 100 // sell 100% of your holding } ``` `bioUpdate` fires when the handle changes their bio, `nameUpdate` when they change their display name. If `nameUpdate` is omitted it takes the value of `bioUpdate`, so a config saved before `nameUpdate` existed keeps firing on name changes when it fires on bio updates. Send `"nameUpdate": false` to fire on bio updates only. ### `engagement` (Engagement) Fires when one of up to 50 handles engages with one of the tweets you list, or with anything posted by the handles you list. ```jsonc "params": { "targetHandles": ["alice", "dave"], // the reactors, 1-50. REQUIRED unless targetHandle is sent // "targetHandle": "alice", // or one reactor (same rule as on mention) "targetTweetIds": ["1234567890"], // watch up to 50 tweets ... OR ... // "targetTweetId": "1234567890", // or one tweet. When targetTweetIds is sent it wins, // and targetTweetId is set to its first entry. // Duplicates are dropped. "reactedToHandles": ["bob", "carol"], // ... watch anything these handles post "targetActions": { // all three REQUIRED, true or false; at least one true "reply": true, "retweet": true, "quote": false }, "keywordInclude": ["yes"], // optional, whole words. NOTE: singular "keyword", not "keywords" "keywordExclude": ["scam"], // optional, whole words "keywordIncludeSubtweetDepth": 0, // optional, 0-8, default 0 "keywordExcludeSubtweetDepth": 0, "tokenAddress": "", // REQUIRED "amount": 0.1 // or "sellPercent": 100 } ``` Set either at least one tweet id (`targetTweetIds` or `targetTweetId`) or a non-empty `reactedToHandles`. With a tweet id set, the config fires on a reaction to any listed tweet and `reactedToHandles` is ignored, so omit the latter. Send `"targetTweetIds": []` with no `targetTweetId` (or with `"targetTweetId": null`) to clear the tweet ids and go back to `reactedToHandles`; an empty list next to a non-empty `targetTweetId` keeps that one id. Each tweet id is the number in the tweet's URL (digits only). A retweet does not always carry the tweet it retweets, so a retweet of a listed tweet may not fire; to catch retweets, list the tweet's author in `reactedToHandles` instead. Exclude lists also block common look-alike spellings (`snipe` also blocks `sn1pe`); include lists need the word as written. Note the singular field names here (`keywordInclude` / `keywordExclude` and their `...SubtweetDepth` pair). Every other mode uses the plural form, and sending the plural form to `engagement` is a `400`. ### Keyword matching semantics Every keyword list in every mode matches **whole words**, case-insensitively. A keyword matches only where both of its edges land on a word boundary, so `orb` matches `orb`, `$ORB`, `#orb`, `orb!`, `(orb)`, `orb/sol` and `orb's`, but NOT `CursorBench`, `absorb`, `orbit` or `orbcoin`. Punctuation is a boundary, not a blocker: `yes` matches `yes.`, `yes;` and `he said "i think yes"`. A word character is any letter, digit or underscore, EXCEPT in scripts written without spaces between words (Chinese, Japanese, Korean, Thai, Khmer, Lao, Myanmar), where those keep plain substring behaviour, because a boundary rule would mean a keyword in them could never match. Every space-separated script gets real word matching, so a Russian keyword `мем` does not fire on `мемкоин`. A keyword you write with leading or trailing punctuation (`$orb`, `#orb`) has the boundary requirement dropped on that edge, so it still matches where you meant it to. Entries are OR-matched: any include entry matching passes, any exclude entry matching skips. Exclude wins over include. An empty or absent include list is no constraint. A keyword may contain spaces (`free mint`); the boundary rule then applies to the outer edges of the whole phrase. No unicode normalization is applied, so a full-width or zero-width-joined keyword will not match. ### Keyword scan depth Each keyword list has a matching `...SubtweetDepth` field: a whole number from 0 to 8 saying how many tweets up the reply / quote chain the keyword scan also reads. `0` scans only the watched handle's own text. Default is `1` for `ca_scanner` (its own text plus the tweet it replies to, quotes or retweets) and `0` for `mention` and `engagement`. A reply that also quotes a tweet counts both at `1`: the tweet it replies to and the tweet it quotes. `ca_scanner` also reads addresses from both. An exclude list never reads past the tweet the trigger was found in: up to the tweet where an include word matched, else the post itself (a retweet: the retweeted tweet); for `ca_scanner`, the tweet each address was found in. ### `follow_unfollow` (Follow / Unfollow) Fires on `(follower, followed)` pairs. Both sides accept up to 50 handles and every combination is matched. ```jsonc "params": { "followerHandles": ["alice", "bob"], // 1-50, who does the (un)following. REQUIRED "followedHandles": ["carol", "dave"], // 1-50, who gets (un)followed. REQUIRED "fireOnFollow": true, // both REQUIRED, true or false; at least one true "fireOnUnfollow": true, "tokenAddress": "", // REQUIRED "amount": 0.1, // buy on follow "sellPercent": 100 // sell on unfollow } ``` This is the one mode where buy and sell can coexist: `amount` fires on follow, `sellPercent` fires on unfollow, which expresses "buy when Alice follows Carol, dump my bag when she unfollows". `amount` is always required: greater than 0 when `fireOnFollow` is true, and it may be `0` for an unfollow-only config. `sellPercent` (1-100) is required when `fireOnUnfollow` is true. Handles here must be 1-15 characters of letters, numbers, or underscores. ### `pfp_update` (PFP update) Fires when any of up to 50 handles changes their profile picture. ```jsonc "params": { "targetHandles": ["alice", "bob"], // 1-50, each 1-15 chars [A-Za-z0-9_]. REQUIRED // unless targetHandle is sent // "targetHandle": "alice", // or one handle (same rule as on mention) "tokenAddress": "", // REQUIRED "amount": 0.1 // or "sellPercent": 100 } ``` ## Buy vs sell For `mention`, `engagement`, and `pfp_update` set **exactly one** of: - `amount`: SOL to buy, must be > 0 - `sellPercent`: percentage of your current holding to sell, 1-100 Sending both is a `400`, and so is sending neither. `follow_unfollow` is the exception described above. A config in sell mode should leave `limitSells` off. ## Handles Handles are stored without the `@` and matched case-insensitively. A leading `@` is stripped for you, so `"@alice"` and `"alice"` are the same thing. `ca_scanner`, `mention`, `engagement` and `pfp_update` all take `targetHandles`. On the last three, a config written with only `targetHandle` keeps working; when reading a config, use `targetHandles` if it is present and not empty, else `targetHandle`, and the same for `targetTweetIds` / `targetTweetId` (which is `null` after the tweet ids were cleared). Sending only `targetHandle` (or only `targetTweetId`) on a config that has the list replaces the whole list with that one value. A config fires once per tweet or profile change, even when that event matches several of its handles or tweet ids. A watched handle (`targetHandles` or `targetHandle`, or `followerHandles` on `follow_unfollow`) that is not available for tracking is rejected when you create a config, when a `PUT` adds it, and whenever you save the config enabled: ``` 400 These handles are not available for tracking: alice, bob. ``` The answer carries `"code": "handle_unavailable"` and may have no `field`. Saves that name handles new to us have their own limit: at most **8 new handles per minute per account**. Past it the API answers `429` with `"code": "handle_checks_limited"` and nothing is changed: wait up to a minute and send it again. Handles already known do not count. A config that names more than 8 new handles is refused with this `429` until its handles are known: each attempt checks up to 8 of them, so send the same save again each minute (about one try per 8 new handles). ## PATCH semantics Every object inside `params` (such as `params.triggers`) also merges key by key, so `{ "params": { "amount": 0.25 } }` changes only the buy size. A `PATCH` of `{ "enabled": false }` alone is always accepted, even when the stored config would no longer pass validation, so a config can always be paused. A `PUT` must carry `modeType`, matching the existing one, and replaces `snipeParams` and `params` wholesale. ## Validation `params` is checked against the schema **of its own mode**, so an `engagement` key sent to a `mention` config is a `400` rather than a silently ignored field. On this tab every `400` also carries a `code`. A `PUT` or `PATCH` with a different `modeType` is a `400`: `The mode of a saved config cannot be changed. Create a new config instead.` ## Examples ```bash BASE=https://eu.slotshark.xyz KEY=your-bearer-key # CA scanner: buy any contract address these two handles tweet, 0.05 SOL a pop curl -s -X POST "$BASE/api/dashboard/twitter/configs" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \ -d '{ "name": "ca alpha", "enabled": true, "modeType": "ca_scanner", "walletPubkey": "", "params": { "targetHandles": ["alice", "bob"], "triggers": { "mainTweet": true, "retweet": true, "quote": false, "reply": false }, "keywordsExclude": ["rug"] }, "maxBuyCount": 10, "snipeParams": { "solAmount": 0.05, "slippage": 50, "limitSells": [ { "type": "pnl", "sellPercent": 50, "value": 100 } ] } }' # Follow / Unfollow: buy when alice follows carol, sell when she unfollows curl -s -X POST "$BASE/api/dashboard/twitter/configs" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \ -d '{ "name": "alice-carol", "enabled": true, "modeType": "follow_unfollow", "walletPubkey": "", "params": { "followerHandles": ["alice"], "followedHandles": ["carol"], "fireOnFollow": true, "fireOnUnfollow": true, "tokenAddress": "", "amount": 0.1, "sellPercent": 100 }, "snipeParams": { "slippage": 40, "sellSlippage": 60 } }' ``` ============================================================================== PART 7: Automation: Copytrade ============================================================================== # Copy-Trade API ## The config object ```jsonc { // -- identity / targeting (top level) -- "name": "Frank", // 1-16 chars, unique per user. REQUIRED "enabled": true, // REQUIRED "targetWallet": "", // base58 address you are copying. REQUIRED // unless targetWallets is sent. // "targetWallets": ["", ""], // or copy up to 50 wallets with one config. // When sent it wins, and targetWallet is set to // its first entry. Duplicates are dropped. // Returned only when it holds 2+ addresses. "ownerWalletPubkey": "", // YOUR SlotShark wallet (must be one of your // active, trade-ready wallets). REQUIRED // -- buy sizing (top level) -- "buyMode": "fixed", // "fixed" | "percent". REQUIRED "buyFixedSol": 0.05, // fixed mode: SOL per copied buy (0 < x < 1000) // "buyMode": "percent", "buyPercent": 20, // percent mode: copy 20% of the target's buy (0 < p <= 100) "maxBuySol": 1.0, // optional cap per buy (0 < x < 1000) "minTargetSpendSol": 0, // optional: only copy if the target spent >= this "maxTargetSpendSol": 100, // optional: only copy if the target spent <= this (< 10000) // -- behaviour (top level) -- "copySells": true, // mirror the target's sells. REQUIRED "firstBuyOnly": false, // only copy each target's FIRST buy of a mint (with several // targetWallets, each target's first buy is copied). REQUIRED // In reverse mode this reads as "first SELL only". "skipTokenDeploys": false, // optional: don't copy the target's buy in the transaction that // creates the coin (their dev buy). Their later buys of that coin // are still copied. With firstBuyOnly on, a coin the target // deploys is never copied, since the deploy is their first buy. // Buys only; omit = off. "skipIfTargetHolds": false, // optional: don't copy the target's buy of a coin it still // holds (an add, including after a partial sell). Its next buy // after it has sold out (under 5% of its bag or under $20 left) // is copied. Coins moved by transfer do not count. Buys only; // ignored in reverse mode; omit = off. "allowedPlatforms": ["pumpfun","raydium","meteora","moonshot","stonkfun","mayhem"], // optional. Omit = all platforms, // including ones added later. Filters BUYS only; sells // always mirror. Ids: Platform ids in PART 5. // -- reverse mode (top level) -- "reverseMode": false, // optional: BUY when the target SELLS. Requires buyMode "fixed"; // copySells is ignored, and min/maxTargetSpendSol are then read // as the target's sell PROCEEDS in SOL. "minTargetSellPct": 100, // optional, REVERSE ONLY (dropped on save when reverseMode is off). "maxTargetSellPct": 100, // Fraction of the target's OWN token balance the sell drained, // 0-100. Both bounds inclusive; omit either for no bound. // min 100 = only when they went to zero (a full exit) // max 50 = only their trims, never a big exit // 100 means the balance actually reached zero, not "rounds to // 100%": a bag one raw unit short of empty does NOT qualify. // Measured against the balance visible in THAT transaction, so a // second token account or a second wallet is invisible to it. // -- firing bound (top level) -- "maxSnipes": 5, // optional cap on total copied BUYS (integer >= 1; omit = unlimited). // Copy-sells keep firing once the cap is reached. // -- fees / slippage / filters / exits (NESTED: this is where sell* live) -- "snipeParams": { "slippage": 20, // buy slippage % "tip": 0.035, // buy tip SOL (omit or 0 = auto) "sellSlippage": 44, // sell override; omit for auto, never the buy value "limitSells": [ // optional auto-exits, one independent set per buy (PART 5) { "type": "pnl", "sellPercent": 50, "value": 100 } // sell 50% at +100% PnL ] } } ``` ### `snipeParams` Copytrade takes `slippage`, `tip`, `priorityFee`, `antimev`, `sellSlippage`, `sellTip`, `sellPriorityFee`, `sellAntimev`, `retries`, `skipIfBought`, `skipIfHeld`, `skipSusPools`, `safeSlippage`, `maxPoolTax`, `minMarketCap`, `maxMarketCap`, `minLiquidity`, `minTokenAgeSecs`, `maxTokenAgeSecs`, `migrationBuffer`, `pileupBufferBps` and `limitSells`. PART 5 has the reference; what is specific to copytrade: | Field | Type | Notes | |-------|------|-------| | `sellSlippage` / `sellTip` / `sellPriorityFee` | number | Sell-side overrides. **Omit for auto:** the live tip and priority fee and 25% slippage. A `sellTip` / `sellPriorityFee` of `0` is auto too. The buy values are never used for a sell. | | `sellAntimev` | boolean | Sells default **on** when `sellAntimev` is unset, whatever `antimev` says. | | `safeSlippage` / `migrationBuffer` / `pileupBufferBps` | advanced | No control for them in the dashboard form; the dashboard keeps them as they are. Leave them alone unless you know you want them. | To set `sellSlippage` or `sellAntimev` back to auto, send a `PUT` without them; `sellTip` / `sellPriorityFee` can instead be PATCHed to `0`. ## Validation errors A `PATCH` is checked as the merged config, so an error can name a field you did not send. Refusals the field docs do not already make obvious: | Field | Message(s) | |-------|------------| | `targetWallet` (also covers `targetWallets`) | `is not a wallet address (it is a pool or program account)` | | `buyMode` | `Reverse mode requires a fixed buy amount (not percent)` | | `buyPercent` | `leave blank in fixed mode` | | `buyFixedSol` | `leave blank in percent mode` | | `maxTargetSpendSol` | `must be at least minTargetSpendSol and less than 10000` | | `maxTargetSellPct` | `must be greater than 0 (leave blank for no ceiling)`, `must be at least minTargetSellPct` | ## Full examples ```bash BASE=https://eu.slotshark.xyz KEY=your-bearer-key # Create curl -s -X POST "$BASE/api/dashboard/copytrade/configs" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \ -d '{ "name": "Frank", "enabled": true, "targetWallet": "", "ownerWalletPubkey": "", "buyMode": "fixed", "buyFixedSol": 0.05, "maxBuySol": 1, "copySells": true, "firstBuyOnly": false, "snipeParams": { "slippage": 20, "sellSlippage": 44 } }' ``` ============================================================================== PART 8: Automation: Callout Sniper and FOMO Thesis ============================================================================== # Callout Sniper API Create, update, and delete Callout sniper configs over HTTP. Same data as the dashboard's **Callout Sniper** tab. A config has one of two trigger modes: - **PumpFun Callout** (the default): buys when a watched caller wallet posts a pump.fun callout. - **FOMO Thesis**: buys when a watched fomo.family trader posts a thesis. See FOMO Thesis mode. Everything else (buy size, coin filters, fees, limit sells, endpoints) is shared by both modes. ## The config object Trigger and buy size are top-level. Fees, slippage, coin filters, the skip switches, and limit sells are nested inside `snipeParams`, as on the other snipers. ```jsonc { // identity "name": "callout-1", // 1-16 chars. REQUIRED "enabled": true, // REQUIRED "walletPubkey": "", // REQUIRED // trigger "callerAddresses": [""], // 1 to 25 callers. REQUIRED "firstCalloutOnly": true, // default TRUE "minHoldSecs": 600, // optional, default 5; caller must have held 600+ seconds "excludedMints": [""], // optional blocklist "keywordsInclude": ["gem"], // optional, buy only when the text has one of these "keywordsExclude": ["rug"], // optional, never buy when the text has any of these // size "solAmount": 0.05, // REQUIRED, > 0 "allowedPlatforms": ["pumpfun", "raydium"], // omit = all venues // bound "maxSnipes": 10, // omit = unlimited // fees, slippage, exits (NESTED) "snipeParams": { "slippage": 50, "tip": 0.01, "maxMarketCap": 5000000, // optional coin filter "limitSells": [ { "type": "pnl", "sellPercent": 50, "value": 100 }, { "type": "time", "sellPercent": 100, "value": 300 } ] } } ``` ### Field reference | Field | Type | Notes | |---|---|---| | `name` | string | Required, 1-16 chars. Compared exactly. Unique per user: a write that reuses another of your configs' names is refused. | | `enabled` | boolean | Required on every write. | | `walletPubkey` | base58 | Required. Must be one of your active wallets. If `enabled` is `true`, the wallet also needs task accounts deployed. | | `callerAddresses` | string[] | The caller wallets this config watches, 1 to 25 base58 addresses. Duplicates are dropped and the order is kept. A callout from any of them triggers the config. The config's settings, its `maxSnipes` and its `snipeCount` are shared by all of them. On `PATCH`, an empty list is not refused: the config keeps only its first stored caller. | | `callerAddress` | base58 | Legacy: `callerAddress`. Still accepted, will stop being supported soon; use `callerAddresses` instead. Responses still carry it; a row with only `callerAddress` watches that one caller. | | `firstCalloutOnly` | boolean | Optional, **defaults to `true`**. `false` fires on every callout of a coin, not just the caller's first. Counted per caller: if two callers in one config each call the same coin for the first time, both fire. Turn on `snipeParams.skipIfBought` to buy a coin once (`skipIfHeld` buys it again after a full exit). | | `minHoldSecs` | number (seconds) | Optional, 0 to 86400, **defaults to `5`**. Only fire if the caller has held the coin for at least this long, counted from their first buy of it (adding to the position does not reset it, selling out does). A coin the caller received but never bought counts from when it arrived, until they buy it. If the caller's position was not seen opening, it counts from the first buy of it we see; with no buy seen either, the check passes. Omitted or `null` means the 5 second default; `0` turns it off. Under 5 seconds is risky: with pump.fun's instant callouts, the caller's copytraders can buy a few blocks before you. | | `minHoldMinutes` | number (minutes) | Legacy: `minHoldMinutes`. Still accepted, will stop being supported soon; use `minHoldSecs` instead. Responses still carry it next to `minHoldSecs`; in a body with both, the one you changed wins. | | `excludedMints` | string[] | Optional, max 200 base58 mints. Omitted or `[]` means none. `null` is rejected. | | `keywordsInclude` | string[] | Optional, max 20 keywords, each 1 to 64 characters. Buy only when the callout's text (FOMO Thesis: the thesis text) contains at least one of them as a whole word, in any case. A callout or thesis with no text is skipped. Omitted or `[]` means no filter. `null` is rejected. | | `keywordsExclude` | string[] | Optional, same limits. Never buy when the text contains any of them as a whole word, in any case, or in a common look-alike spelling (`snipe` also blocks `sn1pe`). Omitted or `[]` means no filter. `null` is rejected. | | `solAmount` | number (SOL) | Required, must be > 0. | | `minAmountOut` | number (tokens) | Legacy: `minAmountOut`. Still accepted (not applied), will stop being supported soon; use `snipeParams.slippage` instead. | | `allowedPlatforms` | string[] | Optional. Platform ids in PART 5; filters buys only. **Omit the field to allow all venues.** Because both `[]` and `null` are refused while an absent key keeps the stored list, **`PATCH` cannot clear the field back to all-allowed. Send a `PUT` without the key to do that** (which is what the dashboard does when you re-tick every venue). | | `maxSnipes` | integer >= 1 | Optional, omit for unlimited. Fire count rules: PART 5. | | `snipeParams` | object | Optional. Send `{}` for empty, never `null`. | Optional numeric fields must be finite and >= 0. The coin filters accept an explicit `null` as "unset"; the other numeric fields of `snipeParams` (`slippage`, `tip`, `priorityFee`, `migrationBuffer`, `maxPoolTax`, `sellTip`, `sellPriorityFee`, `sellSlippage`) reject it. ### `snipeParams` Takes these PART 5 keys: `slippage`, `tip`, `priorityFee`, `antimev`, `safeSlippage`, `retries`, `skipIfBought`, `skipIfHeld`, `skipSusPools`, `maxPoolTax`, `minMarketCap`, `maxMarketCap`, `minLiquidity`, `minTokenAgeSecs`, `maxTokenAgeSecs`, `migrationBuffer` and `limitSells` (exit rungs and their per-rung overrides: PART 5). `tip` / `priorityFee`: omit the key for the automatic values. `0` is not "auto": a `0` tip is raised to the 0.001 SOL floor, a `0` priority fee is used as-is. Accepted by validation but ignored on this sniper: `sellTip`, `sellPriorityFee`, `sellSlippage`, `sellAntimev`, `pileupBufferBps`. Use the per-rung overrides for sell-side fees. ## FOMO Thesis mode A FOMO Thesis config watches one fomo.family trader, by handle, and buys the coin of each thesis they post. Create it with `"mode": "fomoThesis"` and a `fomoHandle` instead of a caller. ```jsonc { "name": "fomo-1", "enabled": true, "walletPubkey": "", // trigger "mode": "fomoThesis", // REQUIRED for this mode, cannot be changed later "fomoHandle": "somehandle", // REQUIRED, the trader's handle exactly as it shows on fomo "firstThesisOnly": true, // default TRUE "excludedMints": [], // size, bound and snipeParams (fees, coin filters, exits): exactly as for a callout config "solAmount": 0.05, "maxSnipes": 10, "snipeParams": { "slippage": 50, "maxMarketCap": 5000000 } } ``` | Field | Type | Notes | |---|---|---| | `mode` | string | `"fomoThesis"` for this mode. Omit (or `"callout"`) for a PumpFun Callout config. Fixed at create: changing it on `PUT` or `PATCH` is rejected with `"code": "mode_immutable"`. A `PUT` on a FOMO config must send `"mode": "fomoThesis"` again: an absent `mode` reads as `"callout"` and is rejected. | | `fomoHandle` | string | Required, at most 64 characters, exactly as it shows on fomo. A leading `@` is optional. Can be changed with `PUT` or `PATCH`. | | `firstThesisOnly` | boolean | Optional, **defaults to `true`**. Only the trader's first thesis on a coin can fire; a later thesis on the same coin does not buy again. | Every other field (`name`, `enabled`, `walletPubkey`, `excludedMints`, `keywordsInclude`, `keywordsExclude` (matched against the thesis text), `solAmount`, the coin filters, `allowedPlatforms`, `maxSnipes`, `snipeParams`) works exactly as documented above for callout configs. Not allowed on a FOMO Thesis config: `callerAddress`, `callerAddresses`, `firstCalloutOnly` (use `firstThesisOnly`), and a non-zero `minHoldSecs` (or `minHoldMinutes`). The reverse also holds: `fomoHandle` and `firstThesisOnly` are rejected on a callout config. ### `fomoCoverage` FOMO rows returned by `GET /configs`, `GET /configs/` and every single-config write carry a read-only `fomoCoverage` (`"live"`, `"queued"`, `"not_found"` or `"unknown"`), the same status the dashboard table shows. `"not_found"` means no fomo account uses that handle (it was mistyped, the account was deleted, or the trader now uses another handle), so the config cannot fire. It is read-only and ignored on a write. ## Server-owned fields Callout rows may also carry a read-only `callerHandle` (the caller's pump.fun handle, for display); it is ignored on a write. ## PATCH semantics ```bash # set the watched callers, keeping filters and fees (send the FULL list) curl -X PATCH "https://eu.slotshark.xyz/api/dashboard/calloutsniper/configs/$ID" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \ -d '{ "callerAddresses": ["", ""] }' ``` The merged result is validated as a whole, so a `PATCH` pointing at a wallet you do not own is rejected and nothing is stored. `PUT` replaces the whole config; an omitted `firstCalloutOnly` goes back to `true`. ## Validation Refusals beyond the field rules above and in PART 5: | Response | Cause | |---|---| | `This wallet has no pump.fun profile, so it can never post a callout. Paste the caller's pump.fun profile wallet, or create a FOMO Thesis config to follow a fomo trader's theses.` | A newly added caller wallet has no pump.fun profile. Carries `"code": "caller_no_pump_profile"` and `"field": "callerAddress"`. | | `Send minHoldSecs or minHoldMinutes, not two different values` | Both sent, disagreeing, and neither is the saved value. Carries `"field": "minHoldSecs"`. | ## Examples ```bash BASE=https://eu.slotshark.xyz KEY=your-bearer-key # create, watching three callers with one budget, buying each coin once curl -s -X POST "$BASE/api/dashboard/calloutsniper/configs" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \ -d '{ "name": "three-callers", "enabled": true, "walletPubkey": "", "callerAddresses": ["", "", ""], "solAmount": 0.05, "maxSnipes": 30, "snipeParams": { "slippage": 50, "skipIfBought": true } }' # create a FOMO Thesis config curl -s -X POST "$BASE/api/dashboard/calloutsniper/configs" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \ -d '{ "name": "fomo-debuts", "enabled": true, "walletPubkey": "", "mode": "fomoThesis", "fomoHandle": "somehandle", "firstThesisOnly": true, "solAmount": 0.05, "maxSnipes": 10, "snipeParams": { "slippage": 50, "tip": 0.01, "priorityFee": 0.005 } }' ``` ============================================================================== PART 9: Automation: Deploy Sniper ============================================================================== # Deploy-Sniper API Everything documented below corresponds to something you can do in the dashboard UI. ## The config object A deploy-sniper config buys a newly deployed token the moment it matches **all** of the config's launch filters. Fees, slippage, and limit-sells live INSIDE the nested `snipeParams` object, NOT at the top level (PART 5). ```jsonc { // -- identity (top level) -- "name": "pepesnipe", // 1-16 chars, unique per user. REQUIRED "enabled": true, // REQUIRED "walletPubkey": "", // YOUR SlotShark wallet (must be one of your // active, trade-ready wallets). REQUIRED // -- buy sizing (top level) -- "solAmount": 0.05, // SOL per snipe. REQUIRED, > 0 "minAmountOut": 0, // optional minimum tokens received (human units) // -- launch filters (top level) -- // At least one of exactNameTicker / nameTickerContains / whitelistedMints / // whitelistedDeployers is REQUIRED. Every filter you set must match. "exactNameTicker": "PEPE", // exact name or ticker, max 64 chars (or null) "nameTickerContains": "pepe, wojak", // comma-separated words, any one matches, max 256 chars (or null) "nameTickerExcludes": "farm, rekt", // comma-separated words, any one blocks, max 256 chars (or null) "whitelistedMints": [], // token addresses "whitelistedDeployers": [], // deployer wallet addresses "allowedPlatforms": ["pumpfun","raydium","meteora","moonshot","stonkfun","mayhem"], // optional. Omit = all platforms, // including ones added later. See Platform ids below. "minDevBuySol": 0.5, // optional, SOL: skip a launch whose create transaction "maxDevBuySol": 5, // bought less / more (>= 0, max >= min; omit or null = no // bound, a min of 0 = no minimum). Not a launch filter on // its own. A launch whose dev buy can't be valued is skipped. // -- firing bound (top level) -- "maxSnipes": 5, // optional cap on total snipes (integer >= 1; omit = unlimited) // -- fees / exits (NESTED) -- "snipeParams": { "slippage": 30, // buy slippage % "tip": 0.01, // buy tip SOL (omit or 0 = auto) "limitSells": [ // optional auto-exits, one independent set per buy (PART 5) { "type": "pnl", "sellPercent": 50, "value": 100 } // sell 50% at +100% PnL ] } } ``` `nameTickerContains` and `nameTickerExcludes` match whole words, not substrings: `not` matches `do not buy` but not `donotbuy`. `nameTickerExcludes` also blocks common look-alike spellings: `snipe` blocks `sn1pe`. ### Platform ids `allowedPlatforms` takes the ids in PART 5 (Platform ids). Only launches are sniped here, so `raydium` means Raydium LaunchLab and `meteora` Meteora Dynamic Bonding Curve. A `PATCH` cannot clear the field (an empty array and `null` are both rejected); to go back to all platforms, send a `PUT` without it. ### `snipeParams` `snipeParams` takes only `slippage`, `tip`, `priorityFee`, `antimev`, `retries`, `maxPoolTax` and `limitSells` (PART 5). Any other key (for example `skipIfBought`, `minMarketCap` or `sellTip`) is refused with a `400` naming it. ## Validation errors A `PATCH` is checked as the merged config, so it can name a field you did not send. Refusals not obvious from the field docs: | Field | Message(s) | |-------|------------| | `filters` | `set at least one filter (exact name, name contains, mints, or deployers)` | | `maxDevBuySol` | `must be at least the min dev buy` | ## Full examples ```bash BASE=https://eu.slotshark.xyz KEY=your-bearer-key # Create curl -s -X POST "$BASE/api/dashboard/sniper/configs" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \ -d '{ "name": "pepesnipe", "enabled": true, "walletPubkey": "", "solAmount": 0.05, "nameTickerContains": "pepe", "maxSnipes": 3, "snipeParams": { "slippage": 30, "tip": 0.01, "limitSells": [ { "type": "pnl", "sellPercent": 100, "value": 100 } ] } }' ``` ============================================================================== PART 10: Automation: PF Claims ============================================================================== # Claim Sniper API Create, update, and delete Claim sniper configs over HTTP. A config watches a set of pump.fun creators and auto-fires a buy when one of them claims the creator fees it has accumulated on a coin. The coin bought is the coin the fees were claimed on. This is the same data the dashboard's **PF Claims** tab reads and writes, so a change made here shows up there immediately. The routes are the PART 5 ones with `` = `claimsniper`. ## The config object Trigger fields and buy size are top-level. Fees, slippage, coin filters, the skip switches, and limit sells live inside the nested `snipeParams` object, as on the other snipers. ```jsonc { // identity "name": "claim-1", // 1-16 chars. REQUIRED "enabled": true, // REQUIRED "walletPubkey": "", // which of your wallets trades. REQUIRED // trigger "creators": ["", ""], // 1 or more. REQUIRED "minClaimSol": 1, // REQUIRED, minimum claim size in SOL. 0 = no floor "firstClaimOnly": true, // default TRUE "excludedMints": [""], // optional. never buy these coins // size "solAmount": 0.05, // buy size in SOL. REQUIRED, must be > 0 "minAmountOut": 250000, // optional floor on tokens received, whole tokens // bound "maxSnipes": 10, // omit = unlimited // fees, slippage, exits (NESTED). Every key: below and PART 5 "snipeParams": { "slippage": 50, "tip": 0.01, "minMarketCap": 20000, // optional coin filter "limitSells": [ { "type": "pnl", "sellPercent": 100, "value": 100 } // sell all at +100% PnL ] } } ``` ### Field reference | Field | Type | Notes | |---|---|---| | `name` | string | See PART 5, Limits. | | `enabled` | boolean | Required on every write. Set `false` to pause without deleting. | | `walletPubkey` | base58 | One of your wallets. See PART 5, Wallet. | | `creators` | string[] | Required, at least one base58 address. Each entry is either a creator wallet (fires when that wallet claims) or a creator's fee account (fires when the creator claims the fees accrued there; if that creator has several live coins, the buy targets the one contributing most to the claim). | | `minClaimSol` | number (SOL) | Required, `>= 0`. The claim must be worth at least this much SOL for the buy to fire. `0` means no floor. | | `firstClaimOnly` | boolean | **Defaults to `true` when omitted.** Only the watched creator's first claim of a coin ever can fire. See the note below. | | `excludedMints` | string[] | Optional per-config coin blocklist, at most 200 base58 mints. This config never buys a listed coin. Omitted or empty means nothing is excluded. See the note below. | | `solAmount` | number (SOL) | Buy size. Required, must be greater than 0. | | `minAmountOut` | number (tokens) | Optional floor on tokens received, in whole tokens, not base units. The buy is refused rather than filled below it. | | `maxSnipes` | integer >= 1 | Cap on fires. Omit for unlimited. See PART 5 (Fire count). | | `snipeParams` | object | Fees, slippage, behaviour flags, limit sells. See below. | ### `snipeParams` Takes the PART 5 keys `slippage` (default `5` here), `tip`, `priorityFee`, `antimev`, `retries`, `skipIfBought`, `skipIfHeld`, `maxPoolTax`, `minMarketCap` / `maxMarketCap`, `minLiquidity`, `minTokenAgeSecs` / `maxTokenAgeSecs` and `limitSells` (rungs as in PART 5, Exit rungs). `safeSlippage`, `migrationBuffer`, `skipSusPools`, `pileupBufferBps`, and the `sellTip` / `sellSlippage` / `sellPriorityFee` / `sellAntimev` overrides pass validation but have no effect here. For sell-side fees, use the per-rung overrides on each limit sell instead. A `minLiquidity` you set also refuses the buy when the pool data is unreadable, like the market cap filters. ### `firstClaimOnly` On by default. Only the watched creator's **first claim of a coin ever** can fire, counting claims made before you created or enabled the config, and whether or not that claim passed your other rules. So if a creator already claimed a coin before, or the first claim comes in below `minClaimSol` or fails a market cap or liquidity filter, no later claim on that coin fires. A creator you just added may be skipped briefly while their past claims are looked up. Turn it off to fire on every qualifying claim of a coin, and pair that with `maxSnipes` so a creator who claims often cannot spend more than you intended. ### `excludedMints` A claim on a listed coin never fires for this config, no matter how large the claim is or which filters it would have passed. - A blocked coin's first claim is **still recorded** while `firstClaimOnly` is on. If you later remove the coin from the list, a claim that happens afterwards is not treated as its first one and will not fire. - A blocked coin **consumes no `maxSnipes` slot**. Empty or omitted means nothing is excluded. `null` is rejected: omit the key instead. ## PATCH semantics `creators`, `excludedMints`, and `snipeParams.limitSells` must each be sent complete. To add one creator, fetch the config, append to the array, and send the whole array back. The merged result is validated as a whole, so a `PATCH` that would empty `creators`, or point at a wallet you do not own, is rejected and nothing is stored. Anything you leave out of a `PUT` body reverts to its default, which for `firstClaimOnly` means back to `true`. ## Examples ```bash BASE=https://eu.slotshark.xyz KEY=your-bearer-key # Watch two creators, buy 0.05 SOL on their first claim of at least 5 SOL per coin curl -s -X POST "$BASE/api/dashboard/claimsniper/configs" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \ -d '{ "name": "big-claims", "enabled": true, "walletPubkey": "", "creators": ["", ""], "minClaimSol": 5, "firstClaimOnly": true, "solAmount": 0.05, "maxSnipes": 20, "snipeParams": { "slippage": 50, "limitSells": [ { "type": "time", "sellPercent": 100, "value": 600 } ] } }' # Fire on EVERY claim from one creator, no threshold, capped at 5 buys curl -s -X POST "$BASE/api/dashboard/claimsniper/configs" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \ -d '{ "name": "all-claims", "enabled": true, "walletPubkey": "", "creators": [""], "minClaimSol": 0, "firstClaimOnly": false, "solAmount": 0.02, "maxSnipes": 5, "snipeParams": { "slippage": 60, "skipIfBought": true } }' # Add a creator to an existing config (send the FULL array) curl -s -X PATCH "$BASE/api/dashboard/claimsniper/configs/$ID" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \ -d '{ "creators": ["", "", ""] }' ``` ============================================================================== PART 11: Automation: Burn Sniper ============================================================================== # Burn Sniper API Create, update, and delete Burn sniper configs over HTTP. A config watches for token burns and auto-fires a buy when one happens: either a wallet you watch burns any token, or a coin you watch gets burned by anybody. This is the same data the dashboard's **Burn Sniper** tab reads and writes, so a change made here shows up there immediately. ## The two watch modes There is no `mode` field. The mode is implied by which watch list you fill in: | Mode | Field | Fires when | |---|---|---| | Wallet mode | `watchWallets` | any wallet in the list burns any token, whatever coin it is | | Token mode | `watchMints` | any of the mints in the list is burned, by anybody | A config may fill both lists at once, in which case it fires on either. At least one of the two must be non-empty: a config that watches neither can never fire and is rejected with `400`. In wallet mode the coin bought is whatever the watched wallet just burned. A burn means tokens sent to a burn address, or destroyed with a burn instruction. Both count, and both feed the same rules below. Burn sniper only buys. It never mirrors a sell. Use `limitSells` for exits. ## The config object ```jsonc { // identity "name": "burn-1", // 1-16 chars. REQUIRED "enabled": true, // REQUIRED "walletPubkey": "", // which of your wallets trades. REQUIRED // watch targets: at least one list non-empty. REQUIRED "watchWallets": ["", ""], "watchMints": [""], // size "solAmount": 0.05, // buy size in SOL. REQUIRED, must be > 0 // burn gate "minBurnPctSupply": 14.7, // percent of total supply burned in this event "firstBurnOnly": true, // default TRUE // bounds "maxSnipes": 10, // omit = unlimited "allowedPlatforms": ["pumpfun", "raydium"], // omit = all platforms // fees, slippage, skips, exits (NESTED) "snipeParams": { "slippage": 50, "tip": 0.01, "minMarketCap": 20000, // optional coin filter "limitSells": [ { "type": "pnl", "sellPercent": 50, "value": 100 }, // sell 50% at +100% PnL { "type": "time", "sellPercent": 100, "value": 300 } // sell 100% after 300s ] } } ``` ### Field reference | Field | Type | Notes | |---|---|---| | `name` | string | 1-16 chars. Must be unique among your burn sniper configs. | | `enabled` | boolean | Required on every write. Set `false` to pause without deleting. | | `walletPubkey` | base58 | One of your own wallets (PART 5). | | `watchWallets` | string[] | Base58 wallet addresses. Every entry is validated. | | `watchMints` | string[] | Base58 mint addresses. Every entry is validated. | | `solAmount` | number (SOL) | Buy size. Required, must be greater than 0. | | `minBurnPctSupply` | number (%) | Floor on how much of total supply this single burn destroyed. **This is a percentage in the 0 to 100 range: a 14.7% burn is `14.7`, not `0.147`.** Compared inclusively, so a burn exactly at the floor passes. Omit for no floor. | | `firstBurnOnly` | boolean | **Defaults to `true` when omitted.** Only the first burn of a coin seen by any burn sniper config on SlotShark can fire, not just the first one this config saw. If that first burn does not pass your other rules, later burns of the same coin will not fire either. Set `false` to allow every qualifying burn. | | `maxSnipes` | integer >= 1 | Cap on fires (PART 5). Omit for unlimited. | | `allowedPlatforms` | string[] | Platform ids from PART 5. **Omit the field to allow all platforms**, including ones added later. | ### `snipeParams` Takes these keys from the PART 5 reference: `slippage`, `tip`, `priorityFee`, `antimev`, `retries`, `skipIfBought`, `skipIfHeld`, `skipSusPools`, `maxPoolTax`, `minMarketCap`, `maxMarketCap`, `minLiquidity`, `minTokenAgeSecs`, `maxTokenAgeSecs`, `limitSells` (exit rungs as in PART 5). A set `minLiquidity` also refuses the buy when the pool's liquidity cannot be read. ## PATCH semantics `PATCH` and `PUT` work as in PART 5. The merged result is validated as a whole, so a `PATCH` that would leave both watch lists empty, or point at a wallet you do not own, is rejected and nothing is stored. A key left out of a `PUT` reverts to its default, which for `firstBurnOnly` means back to `true`. ## Validation Refusals beyond the PART 5 rules and the field docs above: | Response | Cause | |---|---| | `at least one of watchWallets / watchMints is required ...` | Both lists empty. | | `minBurnPctSupply must be a PERCENTAGE between 0 and 100 ...` | Below 0 or above 100. A fraction such as `0.147` is not rejected: it is read as a 0.147% floor, so send `14.7` for 14.7%. | ## Examples ```bash BASE=https://eu.slotshark.xyz KEY=your-bearer-key # Wallet mode: buy 0.05 SOL whenever either of these two wallets burns a token, # but only on burns worth at least 10% of supply, and only once per coin curl -s -X POST "$BASE/api/dashboard/burnsniper/configs" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \ -d '{ "name": "burners", "enabled": true, "walletPubkey": "", "watchWallets": ["", ""], "watchMints": [], "solAmount": 0.05, "minBurnPctSupply": 10, "firstBurnOnly": true, "maxSnipes": 20, "snipeParams": { "slippage": 50, "minLiquidity": 10000, "limitSells": [ { "type": "pnl", "sellPercent": 50, "value": 100 }, { "type": "time", "sellPercent": 100, "value": 600 } ] } }' # Token mode: watch two specific coins and buy on any burn of them, all venues curl -s -X POST "$BASE/api/dashboard/burnsniper/configs" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \ -d '{ "name": "two-coins", "enabled": true, "walletPubkey": "", "watchWallets": [], "watchMints": ["", ""], "solAmount": 0.1, "firstBurnOnly": false, "snipeParams": { "slippage": 40 } }' ```