Overview
The SDK provides methods for developers to manage their accounts, check fee balances, and claim fees:getDevAccountInfo- Get your dev account configuration and settingsgetDevAccountFees- Check fee balances for your dev accountgetDevFeeClaimHistory- View history of completed fee claimsgetFeeClaimAuthorization- Get an authorization signature to claim feesclaimDevFees- High-level method that handles authorization and transaction submission
To avoid ambiguity, we denote the smallest possible multiple of USDC (0.000001 USDC) as one
uusdc,
which stands for µUSDC (micro-USDC), and denote the smallest possible multiple of a contract (0.01 contract)
as one ccontract (centicontract).User-facing USDC balances are specified as fixed-point strings (e.g. "1.2625" for USDC). Contract quantities
in the API and SDK are specified as integer ccontracts strings (e.g. "1050" for 10.50 contracts at precision 2).Configuration
Developer fee methods require configuringdevFlags when creating the client. This enables EIP-712 signature-based authentication with the API.
Getting Account Info
Retrieve your dev account configuration and settings.getDevAccountInfo
Returns
string
Dev account identifier
string
Dev account display name
string
Dev account email
string
Your fee rate in basis points (100 = 1%)
string
Flat fee per trade in µUSDC (integer string)
string
Bison’s share of your gross fees in basis points
string
Chain where fees can be claimed
string
Address that will receive fee payouts
string
Account creation timestamp (ISO 8601)
Example
Checking Fee Balances
Query your dev account’s accumulated fees across different states.getDevAccountFees
devFlags for authentication.
Returns
string
Dev account identifier
string
Dev account display name
string
Fees from trades that haven’t been confirmed yet (integer string)
string
Fees locked for payout (awaiting operator settlement, integer string)
string
Fees available to claim via the vault contract (integer string)
string
Chain where fees can be claimed
string
Address that will receive fee payouts
Example
Fee Claim History
View your past fee claim withdrawals.getDevFeeClaimHistory
Parameters
number
Maximum number of claims to return (default: 50, max: 200)
string
Pagination cursor from a previous response
Returns
array
Array of fee claim records, sorted by most recent first
string
Unique identifier for the claim
string
Chain where the claim was processed
string
Amount claimed in µUSDC (integer string)
string
Address that received the payout
string
Timestamp when the claim was completed (ISO 8601)
number
Number of claims returned in this response
boolean
Whether more claims are available
string
Cursor to fetch the next page (only present if hasMore is true)
Example
Claiming Fees
Claim accumulated fees from the vault contract to your signer address.claimDevFees
This high-level method handles getting the authorization signature and submitting the claim transaction.
Parameters
WalletClient
required
Viem wallet client for signing transactions
PublicClient
required
Viem public client for reading contract state
Returns
Transaction hash of the fee claim transaction.Example
Low-Level Authorization
For advanced use cases, you can get the authorization signature directly.getFeeClaimAuthorization
Example
Fee States
Fees progress through the following states:
Only unclaimed fees can be claimed. Pending and locked fees will become claimable after the settlement process completes.
Error Handling
Important Notes
- All fee amounts are in µUSDC (6 decimal places: 1 USDC = 1,000,000 µUSDC)
- Fee claim authorizations expire after 30 seconds
- You can only have one pending claim authorization at a time
- Fees are paid out to the signer address configured for your dev account
- Use
getDevAccountFeesto check your balance before attempting to claim - The SDK automatically handles EIP-712 authentication when
devFlagsis configured