Skip to main content
Remove one or more wallets from your private BYOB pool. Wallets not in the pool (or already removed) are silently skipped — removed reflects only how many wallets were actually present.

​
Request body

​
Response fields

​
Example: remove an existing wallet

Request:
Response (200 OK):
Only the first wallet was actually in the pool — the second was never tracked, so it’s a silent no-op. The response tells you exactly how many were touched.

​
Example: idempotent re-remove

Calling delete on a wallet already removed is safe — returns removed: 0 with no error. Request:
Response (200 OK):
This makes “set my pool to exactly this list” workflows simple — DELETE old, POST new, both safe to re-run.

​
Errors

400 Missing or invalid addresses:
Same auth/rate-limit errors as the rest of the /v2/copy-pnl/* family.

​
Notes

  • Removal is per-tenant. Removing a wallet from your pool does NOT remove it from the global refresh queue if other tenants still track it — the wallet’s score keeps refreshing for them. Your private query just stops returning that wallet.
  • Cached scores survive briefly. The wallet’s last-computed score stays in our cache (24h TTL). If you re-add the same wallet within 24h, the leaderboard will show its existing score immediately while the on-add freshening kicks off a fresh recompute.
  • No bulk-clear endpoint. To wipe your entire pool, GET your wallet list first, then DELETE all of them in chunks of 1000.