Manager API: dashboard sign-in, strategy and SMA account reads, self-service keys, and a reshaped fee ledger
The Manager API reference and guide now cover everything the API serves. It accepts a signed-in session on the Treasures dashboard alongside your manager API key, adds reads for the strategies assigned to you and for the separately managed accounts of an SMA strategy, and lets a dashboard session mint and revoke your keys. Two changes reach existing key callers and are marked Action: GET /fees has a new response shape, and a request with no credential now answers 401 unauthorized.
What changed
Action: the fee ledger is reshaped. GET /fees no longer returns owed_usdc, pending_usdc, paid_usdc or payouts[]. Payouts are no longer booked through this API. The ledger now reports the part of your share paid to your fee address on-chain, inside the transaction that collects the fee (received_usdc); any part not paid that way is counted in platform_usdc.
- The totals are
uncollected_usdc,collected_usdc,received_usdc,platform_usdcandlifetime_usdc. Onlyreceived_usdcis your share; the others are whole fees, what your followers pay. fee_addressesis the fee address registered for you on each address family (sol,evm), ornull.- In each row of
collections[],leader_share_usdcis renamedmanager_share_usdc. The row gainsreceived_usdc, and for a separately managed account itsaccountaddress and thetransactionsthat collected the fee.
Action: no credential is 401 unauthorized. A request that carries no credential at all used to answer 401 invalid_api_key. A key that is present but malformed, unknown or revoked still answers invalid_api_key or key_revoked, so a system that always sends its key sees no change.
A second credential: the dashboard session. Your own login on the Treasures dashboard, as a Member of the Organization your manager account belongs to, is accepted on every route. The headers it sends are in the Manager API reference.
- Publishing a book from a session (
POST /strategies/{strategyId}/signals) and minting a key need a sign-in made in the last 15 minutes, or are refused403 reauth_required. If Treasures cannot confirm the sign-in, the request is refused503 sign_in_check_unavailableand nothing is written. Neither answer is ever given to an API key. - A Member who is not an Admin can do only what its permissions grant (
403 permission_deniedotherwise). A login in more than one Organization names the one it acts for inX-Organization-Id. - New refusals on every route:
403 manager_not_linked,403 organization_suspendedand403 permission_denied.403 manager_suspendednow refuses your dashboard session as well as your keys. - When
X-API-Keyis present it is the only credential checked. - Sessions have their own budget of 120 requests per minute per manager. The 60 per minute your keys share is unchanged, and neither budget can use up the other.
Reading your strategies, with a key or a session:
GET /strategies: every strategy assigned to you, at every status includingdraft, with its newest book, its live follower count, itsaudience(retailorsma) and the total value of its followers' portfolios once at least three followers contribute to it.GET /strategies/{strategyId}/signals: every book published into the strategy at every status, newest first, with why the last plan attempt gave up and, once a book is final and at least three followers hold orders on it, its order counts by state.GET /strategies/{strategyId}/performance: the strategy's daily performance line, a backtest where one was published followed by the live model. Served fordraftstrategies too.
SMA accounts, for a strategy whose audience is sma (a retail strategy answers 404 strategy_not_sma). Each account is named by its own wallet addresses, never by the client behind it, and the three-follower minimum does not apply.
GET /strategies/{strategyId}/accounts: every account assigned to the strategy, with its state and latest daily valuation, plus totals across the accounts.GET /strategies/{strategyId}/accounts/{address}/fills: every order that filled for one account, with its USDC amount and each leg's chain and transaction hash.GET /strategies/{strategyId}/accounts/{address}/holdings: a live read of one account's positions, stablecoins and gas, answered503instead of a partial figure when a read does not complete. It has its own budget of 20 calls a minute per credential kind, and answers503 portfolio_busywithRetry-Afterfrom 00:03 to 00:40 UTC, around the daily valuation.GET /strategies/{strategyId}/accounts/{address}/performance: every daily valuation of one account, oldest first, numbered by assignment.GET /strategies/{strategyId}/orders: every fill across the strategy's accounts, newest first, optionally narrowed to onesignal_id.
Keys, from a dashboard session only (an API key is refused 403 session_required):
GET /keys,POST /keysandDELETE /keys/{keyId}list, mint and revoke your API keys. A minted key is shown once. You may hold 10 active keys and make 20 self-service mints in any 24 hours. Revoking needs no recent sign-in, so a leaked key can always be shut off at once.
Smaller changes.
- Every
{strategyId}accepts the strategy's slug as well as itscst_id. - A query parameter on a route that takes none, publishing included, is refused
400 invalid_request. - A
stalebook, queued for the next session, starts 30 minutes after that session's open.
What to do
- Action: if you read
GET /fees, move to the new fields.owed_usdc,pending_usdc,paid_usdcandpayouts[]are gone, andleader_share_usdcon a collection is nowmanager_share_usdc. - Action: if you match on
401 invalid_api_keyto detect a missing key, match401 unauthorizedas well. - Otherwise nothing: publishing with a key is unchanged. The guide is Managing a Strategy.