All requests require an API key via the
X-API-Key header.
See Authentication for details.Overview
GET /v1/streams/{id}/wallets returns the wallets that currently have snapshot data for a specific stream, scoped to the organization that owns the API key.
Each returned wallet includes only its latest available snapshot for that stream. This makes the endpoint suitable for leaderboard views, partner dashboards, stream monitoring UIs, CSV exports, and paginated reporting workflows where you need a compact wallet-level summary instead of the full historical timeline.
Results are ordered by
lastSnapshot.rewardsAccumulated in descending order, so the first wallets in the response are the ones with the highest accumulated rewards.Endpoint
Parameters
Path ParametersStream identifier. This is the unique UUID of the stream whose participant wallets you want to inspect. The API first verifies that this stream belongs to the organization associated with the API key, so a valid UUID alone is not enough: the stream must also be in your organization scope.
Page number for the paginated result set. Use this to move through the wallet list in stable chunks. Values lower than
1 are normalized by the backend to 1.Number of wallets to return per page. This is useful when building dashboards, tables, or exports. Values lower than
1 are normalized to 20, and values above 100 are capped to 100 by the backend.Response Example
Response Semantics
Each row contains the latest snapshot only
Each row contains the latest snapshot only
This endpoint does not return full wallet history. Instead, each wallet entry contains a
lastSnapshot object representing the most recent snapshot currently available for that wallet in the stream.An empty page is a valid response
An empty page is a valid response
If the stream exists but there are no wallet snapshots yet, or if you request a page beyond the available data, the endpoint returns
data: [] together with pagination metadata instead of failing.The stream is organization-scoped
The stream is organization-scoped
Even if you know a valid stream UUID, the API only returns data when that stream belongs to the organization associated with the API key.
Response Fields
Paginated list of wallets that have snapshot data for the requested stream.
Pagination metadata describing the current page and the total size of the result set.
WalletWithLastSnapshot
Wallet address that participated in the stream. This is the address whose balances or positions were tracked during snapshot computation. It is returned as an EVM address string.
Most recent snapshot recorded for that wallet in this stream. This object summarizes the wallet’s latest reward accumulation and TVL metrics.
WalletSnapshot
Effective timestamp of the snapshot. This is the time bucket the metrics correspond to, not necessarily the exact database write time.
Total rewards accumulated by the wallet at this snapshot, expressed in base units. For token streams, that means token wei-like units according to the reward asset decimals. For point streams, this is the accumulated point amount in the point’s base precision. This field represents the reward amount after adapters have been applied (post-adapter).
Base accumulation value used by Turtle’s internal reward accounting. This value reflects the accumulated rewards before adapters are applied (pre-adapter).
Timestamp when this wallet snapshot row was first created in Turtle’s backend.
Timestamp of the latest update applied to this wallet snapshot row.
Time-weighted-average (TWA) USD Total Value Locked (TVL) for the wallet after adapters have been applied.
TWA USD TVL for the wallet before adapters are applied.
TWA USD TVL of the wallet’s net position. Calculated as TWA of min(0, tokenBalance - startBalance) * priceUSD, where
startBalance is the user’s token balance at the stream’s startTimestamp. Both priceUSD and tokenBalance are time-weighted averages (TWA).TWA USD TVL restricted to Turtle users and windowed to each user’s sign-up timestamp. This measures the portion of the wallet’s TVL that should be considered for Turtle-specific user eligibility and reward rules.
Turtle-equivalent of
netTvl: a TWA net position calculated using the user’s token balance at their sign-up timestamp as the reference instead of the stream startTimestamp.Strategy-specific metrics captured for the wallet snapshot. Treat this field as extensible JSON. Currently, it contains the wallet’s TWA token balance for the snapshot.
PaginationResponse
Current page returned by the backend after normalization.
Number of items returned per page after normalization or capping.
Total number of records available for the stream across all pages.
Total number of available pages for the current
limit.Integration Notes
Use this endpoint for tables and leaderboards
Use this endpoint for tables and leaderboards
Because this endpoint returns one row per wallet with only the latest snapshot, it is the best choice for ranking views, summary widgets, CSV exports, and admin pages where full historical data would be too heavy.
Amounts are returned as strings on purpose
Amounts are returned as strings on purpose
Reward amounts are serialized as strings to avoid precision loss in JavaScript and other environments that cannot safely represent very large integers. Keep them as strings in transit and convert them with a big-number library only when you need arithmetic.
Use the single-wallet endpoint for history
Use the single-wallet endpoint for history
If you need the full timeline of snapshots for one wallet, call Get Wallet Data instead of this paginated summary endpoint.
Error Handling
Missing or invalid API key
Missing or invalid API key
Status Code: 401 UnauthorizedSolution: Pass a valid
X-API-Key header belonging to an organization-scoped API key.Stream not found in your organization scope
Stream not found in your organization scope
Status Code: 404 Not FoundThis happens when the
id path parameter does not correspond to a stream owned by the organization associated with the API key.Unexpected internal error
Unexpected internal error
Status Code: 500 Internal Server ErrorSolution: Retry the request and contact Turtle if the issue persists.

