Documentation Index
Fetch the complete documentation index at: https://docs.turtle.xyz/llms.txt
Use this file to discover all available pages before exploring further.
This endpoint is permissionless — no API key is required. Merkle proofs are public data that anyone can verify on-chain.
Overview
GET /v1/streams/merkle_proofs returns Merkle proofs for a wallet across one or more token streams. Each proof contains everything needed to call claim() on the stream’s smart contract: the cumulative allocation amount, the proof array, the contract address, and the chain ID.
Use this endpoint when building a claim UI on a partner website or in any frontend that needs to submit on-chain claim transactions.
This endpoint returns proofs for token-based streams only. Point-based streams do not have on-chain Merkle trees.
Endpoint
streamIds parameter:
The user’s EVM wallet address.
One or more stream UUIDs to fetch proofs for. Repeat the parameter for multiple streams. You can find your stream IDs via Get Streams or from your Turtle dashboard.
Response Example
Response Fields
Array of Merkle proofs, one per requested stream where the wallet has an allocation.
StreamMerkleProof
The stream this proof belongs to.
Decimal EVM chain ID where the stream contract is deployed (e.g.
8453 for Base, 1 for Ethereum).The stream contract address to call
claim() on.Total cumulative allocation in raw token units. This is the total ever allocated to the wallet, not the unclaimed balance. The contract tracks what has already been claimed. Call
getRewardToken() on the stream contract to look up the token’s decimals for display formatting.Array of
bytes32 hashes for Merkle verification, passed directly to the contract’s claim() function.The Merkle root hash this proof was generated against.
ISO 8601 timestamp of the Merkle root used for validation. Passed to the contract as a
uint40.Operational Notes
Cumulative amount model
Cumulative amount model
The
amount field is cumulative — it represents the wallet’s total allocation across all snapshots, not a per-snapshot delta. The on-chain contract tracks how much has already been claimed and releases the difference when claim() is called.Proof caching
Proof caching
Proofs are recomputed on each snapshot cycle. Between snapshots, the same proof data is returned. There is no need to poll this endpoint — fetch once when the user is ready to claim.
Empty proofs array
Empty proofs array
If the wallet has no allocation in any of the requested streams, the
proofs array will be empty. This is not an error — it means the wallet is not a participant in those streams.Using proofs on-chain
Using proofs on-chain
Pass
amount, timestamp, and proof directly to the stream contract’s claim() function. See Claim Rewards for the full on-chain integration guide.Error Handling
Missing required parameters
Missing required parameters
Status Code: 400 Bad RequestSolution: Ensure both
wallet and at least one streamIds parameter are present.Unexpected internal error
Unexpected internal error
Status Code: 500 Internal Server ErrorSolution: Retry the request and contact Turtle if the issue persists.

