The signal history of your strategy
/strategies /{strategyId} /signalsEvery book and trade event published into this strategy, by you or by the strategy's
source, at every status, newest first: including books that were superseded by a later
one on the same trading day and books Treasures could not plan (not_plannable). Pass
status to see one status only. Rebooks Treasures issues on its own (a rebalance for a
follower who joined late, a retry of a failed order) and the sells that close one
follower's position are not listed.
-
summarydescribes the book: how many positions, the weight deployed, and the five largest positions.nullwhen the stored signal cannot be read; the row is still listed. -
plan_attemptsis how many times Treasures tried to plan the signal into orders. -
plan_errorsays why the last attempt gave up, or why the signal lapsed with nothing owed; seePlanError. A reason that describes the followers (no_active_followers,all_follows_in_flight,nothing_owed) isnullwhen fewer than three followers were following when the signal was published, or when fewer than three follow the strategy now. On an SMA strategy (audience: sma) that minimum does not apply, unless anyone other than a separately managed account has ever followed it, when such a reason is alwaysnull. -
orders.by_statecounts the orders the signal produced, by state. It is served once the signal has a final status (completed,lapsedorhalted), every order on it is terminal and at least three followers hold orders on it; otherwisenull, so it is never a count still moving. It isnullon every other status,supersededandnot_plannableincluded, and while a lapsed or halted signal still has an order in progress.Below three followers the counts would describe one follower's own balance, limits or allocation. On an SMA strategy (
audience: sma) that minimum does not apply, unless anyone other than a separately managed account has ever followed it, whenordersis alwaysnull. States with no orders are left out.
Pass next_cursor back as cursor to page; null means you have seen them all.
Request
Responses
- 200
- 400
- 401
- 403
- 429
OK
invalid_request: an unknown query parameter, limit outside 1 to 100, an unknown status, or cursor: malformed (restart from the first page). invalid_strategy_id when the path segment is empty or longer than 64 characters.
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.
strategy_forbidden: this strategy is not assigned to you. The same response is returned for a strategy id that does not exist, so the id space cannot be probed; check the id with your Treasures contact. It is decided before the query string is read.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_suspendedandpermission_deniedas on every 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.