Skip to main content

Claim fees

POST 
/token-launches/:tokenAddress/fees/claim

Collect your share of trading fees for a Bankr-launched token.

Handles Doppler (pool fee-share beneficiary), Clanker (WETH reward-recipient) and Bankr Launch v3 (the launch's fee recipient, claiming from its Fee Locker or Creator Fee Vault) launches — the server auto-detects which protocol the token was launched on and constructs the appropriate transaction. Signs and broadcasts the transaction server-side and returns the final receipt in one call. A v3 launch paid in one asset (the default quote fee mode) can answer 403 no_claimable_fees while its fees are still being converted.

Clanker semantics: Clanker's locker sweeps WETH rewards for a reward-recipient across all Clanker tokens in one transaction — there is no per-token Clanker claim. The tokenAddress path param is used for the activity lookup and response description; the on-chain call collects every pending WETH reward for the caller's wallet. Doppler claims remain per-pool.

Replaces the prior two-call flow (POST /agent/doppler/claim → POST /wallet/submit) and the per-protocol legacy endpoints (/user/doppler/claim, /user/doppler/execute-claim, /clanker/claim, /agent/doppler/claim). Those routes still respond, with Deprecation and Sunset response headers, but their sunset date has passed.

Authentication: requires a Bankr user API key with walletApiEnabled. Pass as X-API-Key: bk_usr_{keyId}_{secret} (preferred) or Authorization: Bearer <same>. The key must not be readOnly, and the provisioning org (if any) must have the walletApi capability enabled.

External wallets (Safe multisig, hardware wallets, third-party signers): use POST /public/doppler/build-claim instead — that endpoint returns unsigned calldata for external signing and supports batching.

Request​

Responses​

Claim transaction submitted and confirmed.