Skip to main content

Your fee ledger (what you are owed, what is pending, what has been paid)

GET 
/fees

Treasures collects management and performance fees from the followers of your strategy, and a share of every collection is yours. This is the ledger of that share, for the manager the key belongs to. There is no manager id in the path.

  • owed_usdc: your share of every collection that no payout has claimed yet.
  • pending_usdc: the sum of payouts Treasures has booked but not yet paid.
  • paid_usdc: the sum of payouts that have been paid, each with the transaction hash of the transfer.

payouts lists your 200 most recent payouts, newest first, and is not paginated; the three totals are computed over every payout, so a manager with more than 200 payouts still sees correct totals. A payout is pending from the moment it is booked, then paid (with tx_hash and paid_at) or void (cancelled before payment; the collections it covered are owed to you again). to_address is the payout address Treasures registered for you at the time the payout was booked. An EVM address is echoed in checksum form.

collections is the paged half: every collection from a follower of your strategy, newest first. amount_usdc is the whole fee collected; leader_share_usdc is the part that is yours. Pass next_cursor back as cursor to page; null means you have seen them all.

The totals, the payout list and the collections page are read in one snapshot, so they never disagree about a payout booked while you were reading.

Read-only: your payout address is set by Treasures and cannot be changed from this API, so a leaked key can learn a balance but cannot redirect it. Rotate a leaked key by asking your Treasures contact to revoke it and issue a new one.

Request​

Responses​

OK