Treasures Finance Manager API
API for fund managers who publish a strategy on Treasures. You publish the target weights of the strategy you manage; Treasures rebalances every follower's wallet towards them and pays you your share of the fees those followers pay.
What you can do. Two things: publish a book (POST /strategies/{strategyId}/signals)
and read your fee ledger (GET /fees). You never see, and cannot ask about, an individual
follower. Follower counts are the only aggregate you receive.
Onboarding. Treasures creates your manager account, assigns the strategy you will
publish into, and hands you a manager API key (cmk_…) out of band. Ask your Treasures
contact for a key, for a strategy to be assigned to you, or to set the address your fees
are paid to. None of those can be done through this API.
Auth. Every route requires your manager API key in the X-API-Key header. There is
no anonymous route on this API. See ManagerApiKey.
Wire format. Weights and USDC amounts are JSON strings to avoid float drift.
Timestamps are ISO-8601 UTC strings; trading_day is a YYYY-MM-DD date.
Rate limits. 60 requests per minute per manager, shared by every key you hold.
A 429 carries a Retry-After header in seconds; wait that long before retrying.
Bodies must be JSON. Send Content-Type: application/json on every request that
carries a body; any other content type is refused 415 before the body is read.
Authentication
- API Key: ManagerApiKey
Your manager API key, cmk_ followed by 24 alphanumeric characters, issued by Treasures out of band. It is shown to you once at issue and cannot be retrieved afterwards, so store it when you receive it; if you lose it, ask Treasures to revoke it and issue a new one. Required on every route. A missing, malformed or unknown key is 401 invalid_api_key and a key Treasures has revoked is 401 key_revoked. A key for a different Treasures API (an integrator tik_ key, a wallet twk_ key) is not accepted here.
Security Scheme Type: | apiKey |
|---|---|
Header parameter name: | X-API-Key |