Your fee ledger (your share of each collection, and what reached you on-chain)
/feesTreasures 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 credential belongs to. There is no manager id in the path.
received_usdc: your share paid to your fee address on-chain, inside the same transaction that collected the fee.uncollected_usdc: fees charged to your followers and not yet recorded as collected. Collection runs on a weekly pass, when a follower exits, and on demand by Treasures, and can be held back, so it has no fixed date. A fee whose transfer has gone through counts here until its collection is recorded.collected_usdc: the whole fee of every collection, all time.platform_usdc:collected_usdcminusreceived_usdc, the part of collected fees paid to the Treasures fee wallet. It includes any part of your share not paid to your fee address on-chain: wherereceived_usdcis 0, that is your whole share.lifetime_usdc:uncollected_usdcpluscollected_usdc.fee_addresses: the fee address Treasures has registered for you on each address family (sol,evm),nullwhere none is registered.
Every total but received_usdc is a whole fee (what your followers pay), not your share.
Your share of a fee is fixed only when it is collected, so uncollected_usdc has none.
collected_usdc equals received_usdc plus platform_usdc whenever platform_usdc is
above 0; platform_usdc never goes below 0.
A collection counts for whoever managed its strategy when it was collected. An uncollected
fee counts for the strategy's current manager, so a strategy that moves to another manager
takes its uncollected fees with it and leaves its collections. lifetime_usdc can fall: a
fee waived when a follower closes, a strategy moving away, fees switched off
(uncollected_usdc then reads 0), or Treasures moving the date fees count from to a later
one or cancelling uncollected fees charged before a date. A collection that takes more than
was owed adds the difference.
collections is the paged half: every collection from a follower of your strategy, newest
first. amount_usdc is the whole fee collected; manager_share_usdc is the part that is
yours, and received_usdc is the part of it paid to your fee address on-chain. For a separately managed
account, account is that account's address (the same address the accounts routes
take) and transactions lists the on-chain transactions that collected the fee; for any
other follower both are empty (null, []). Pass next_cursor back as cursor to page;
null means you have seen them all.
A dashboard Member that does not also hold invested_wallets:view gets account and
transactions empty for every collection; the amounts are unchanged.
The totals and the collections page are read in one snapshot, so they never disagree about a collection recorded while you were reading. A collection appears once its fee transactions have settled.
Your fee addresses are set by Treasures and cannot be changed from this API, so a leaked
key or session can read the ledger and the addresses but cannot redirect a fee. An EVM
address is echoed in checksum form. If a key leaks, revoke it (DELETE /keys/{keyId}) and
mint a replacement (POST /keys) from a signed-in dashboard session, or ask Treasures to.
Request
Responses
- 200
- 400
- 401
- 403
- 429
OK
invalid_request: an unknown query parameter, limit outside 1–100, or cursor: malformed (restart from the first page).
unauthorized: no credential was sent at all (breaking change: this used to beinvalid_api_key), or a dashboard session failed verification: the access token is missing, malformed or expired, or the identity token is missing or belongs to a different login.invalid_api_key:X-API-Keyis malformed, unknown, or belongs to a different Treasures API.key_revoked: this key has been revoked; mint a new one or ask Treasures.
manager_suspended: your account is suspended; every key you hold and your dashboard session are refused until Treasures reactivates it.manager_not_linked: a valid dashboard login that is a Member of no Organization with a manager account.organization_suspended: your Organization is suspended; every Member session is refused, your keys keep working.permission_denied: your Member permissions do not grant this route.
More than 60 requests in the last minute across every key you hold, or more than 120 across your dashboard sessions; each kind has its own budget. The Retry-After header carries the seconds to wait.
Response Headers
Seconds to wait before retrying.