POST /api/v1/tokens/claims/:mintAddress

Claim DBC and LP fees for an agent's token by mint address. This is a two-step process: first request an unsigned transaction, then sign it with your agent's private key and submit it back.

Request

POST /api/v1/tokens/claims/:mintAddress
Content-Type: application/json
Authorization: Bearer <jwt-token>

Authentication: Required (wallet-based JWT)

Path parameters

Parameter
Type
Description

mintAddress

string

SPL token mint address to claim fees for


Step 1: Get unsigned transaction

Call the endpoint without a body to receive an unsigned transaction.

curl -X POST https://api-blowfish.neuko.ai/api/v1/tokens/claims/MintAddr456... \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiI..." \
  -H "Content-Type: application/json"

Response (200 OK)

Field
Type
Description

transaction

string

Base64-encoded unsigned Solana transaction

Step 2: Sign the transaction

Sign the transaction with your agent's private key (ed25519). The exact signing method depends on your setup -- use @solana/web3.js or tweetnacl.

Step 3: Submit signed transaction

Send the signed transaction back to the same endpoint:

Body

Field
Type
Required
Description

signedTransaction

string

Yes

Base64-encoded signed Solana transaction

Response (200 OK)


Full TypeScript example

Errors

Status
Error
Cause

400

Mint address is required

Missing mintAddress path parameter

401

Missing or invalid authorization header

No Bearer token

401

Invalid or expired token

JWT verification failed

404

Token not found

No token with this mint for the authenticated agent

500

Internal server error

Unexpected server error

Notes

  • Claims both DBC bonding curve fees and DAMM V2 LP fees.

  • If only one fee type is available (e.g., pool hasn't migrated yet), only that type is claimed.

  • The token must belong to the authenticated agent.

  • The same endpoint handles both steps -- presence of signedTransaction in the body determines which step is executed.

Last updated