All requests require an API key via the
X-API-Key header.
See Authentication for details.Overview
GET /v1/streams/{id}/wallets/{address} returns the full snapshot history for one wallet inside one stream, as long as the stream belongs to the organization associated with the API key.
Use this endpoint when you need a wallet-level drilldown: detailed reward history, charting, reconciliation, user support tooling, or a per-wallet export that includes every available snapshot instead of just the most recent one.
The response includes both the wallet history and the parent
stream object. This lets you render a wallet-detail page without making an extra call to the streams listing endpoint.Endpoint
Parameters
Path ParametersStream identifier. This selects the stream whose wallet history you want to inspect. The backend validates both that the UUID is syntactically correct and that the stream belongs to the organization associated with the API key.
Wallet address to inspect within the selected stream. This should be the EVM address whose snapshot history you want to retrieve. Use a standard hex address such as
0x1111111111111111111111111111111111111111; checksummed addresses are recommended for readability, although the backend ultimately resolves the address value against stored wallet records.Response Example
Response Semantics
This endpoint returns full wallet history
This endpoint returns full wallet history
Unlike the list-wallets endpoint, this response includes the full
snapshots array available for the requested wallet in the selected stream.A wallet must have snapshot records to be returned
A wallet must have snapshot records to be returned
If the stream exists but the requested address has no stored snapshots in that stream, the endpoint returns
404 Not Found.The nested stream object is the same schema used elsewhere
The nested stream object is the same schema used elsewhere
The
wallet.stream object follows the same Stream schema documented in Get Streams, so you can reuse the same client-side types for both endpoints.Response Fields
Wallet-specific stream data, including the wallet identity, the complete snapshot history found for that wallet in the stream, and the parent
Stream object.WalletData
Identifier of the stream the wallet data belongs to. This duplicates the
id path parameter in the response so downstream systems can store the wallet payload without separately carrying request context.Wallet address whose history is being returned.
Full list of snapshots found for this wallet in the stream. Each item represents one recorded point-in-time state used for reward accumulation and wallet-level TVL accounting. For the canonical
WalletSnapshot field definitions, see the WalletSnapshot section on the Get Stream Wallets page.Parent stream object associated with the wallet snapshots. This uses the same schema documented in Get Streams.
Stream
The nested stream field uses the same Stream schema returned by Get Streams, including fields such as id, chainId, contractAddress, customArgs, lastSnapshot, committedSnapshot, point, and rewardToken.
This means:
- you can reuse the same TypeScript or backend DTO definitions for stream parsing,
- you do not need a second request to resolve the stream metadata for the wallet detail view,
- and you can display stream configuration and wallet history together in one screen.
Integration Notes
Use this endpoint for charts and wallet drilldowns
Use this endpoint for charts and wallet drilldowns
Because the full
snapshots array is included, this endpoint is the correct source for historical charts, cumulative reward plots, wallet audits, and customer support views.Large integers must be handled with big-number tooling
Large integers must be handled with big-number tooling
Reward fields are returned as strings because they may exceed the safe integer range of JavaScript numbers. Use a big-number library if you need arithmetic or unit conversion.
Use the list endpoint for performance-sensitive overviews
Use the list endpoint for performance-sensitive overviews
If you only need one row per wallet for a summary table, use Get Stream Wallets instead. It is more compact because it returns only the latest snapshot per wallet.
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 or wallet has no snapshots
Stream not found or wallet has no snapshots
Status Code: 404 Not FoundThis status is returned either when the stream does not belong to your organization scope or when the specified wallet address has no snapshot history in that stream.
Unexpected internal error
Unexpected internal error
Status Code: 500 Internal Server ErrorSolution: Retry the request and contact Turtle if the issue persists.

