curl --request GET \
--url https://api.yieldpoint.io/v1/transactions/{address}const options = {method: 'GET'};
fetch('https://api.yieldpoint.io/v1/transactions/{address}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.yieldpoint.io/v1/transactions/{address}"
response = requests.get(url)
print(response.text)[
{
"id": "<string>",
"requestedOnChainId": 123,
"claimedOnChainId": 123,
"kind": "mint",
"product": "UTY",
"vault": "<string>",
"direction": {
"from": "USDC",
"to": "USDC"
},
"sent": {
"value": "<string>",
"token": "USDC",
"address": "<string>",
"decimals": 123
},
"received": {
"value": "<string>",
"token": "USDC",
"address": "<string>",
"decimals": 123
},
"status": "completed",
"hash": "<string>",
"blockNumber": 123,
"timestamp": 123,
"requestId": 123,
"requestedAt": 123,
"cooldownEndsAt": 123,
"claimedAt": 123,
"claimedHash": "<string>",
"hubTx": "<string>",
"hubTimestamp": 123,
"hubBlockNumber": 123
}
]{
"error": "<string>",
"message": "<string>",
"traceId": "<string>",
"validation": [
"<string>"
]
}Returns multi-chain transaction history for a given wallet address.
Returns up to 500 lifecycle rows ordered newest-first. Each request
targets a single chain via the required chainId query parameter:
8453 (Base, hub), 43114 (Avalanche, spoke), or 747474 (Katana, spoke).
The query parameter filters by requestedOnChainId — the chain where
the activity was initiated.
Three kind values: mint (USDC → UTY), deposit (UTY → yUTY), and
withdrawal. yUTY withdrawals follow a cooldown → claimable → claimed
lifecycle; UTY withdrawals are born at claimed (instant path).
Each row carries both requestedOnChainId (where the activity was
initiated) and claimedOnChainId (where the claim was settled — the
hub for “claim all on Base”, the spoke for OFT bridge-back). These can
differ: a request initiated on Avalanche can be claimed on Base, or
bridged back to Katana. Calling per chain is the canonical way to
render a multi-chain history; the API does not aggregate across chains
in a single response.
curl --request GET \
--url https://api.yieldpoint.io/v1/transactions/{address}const options = {method: 'GET'};
fetch('https://api.yieldpoint.io/v1/transactions/{address}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.yieldpoint.io/v1/transactions/{address}"
response = requests.get(url)
print(response.text)[
{
"id": "<string>",
"requestedOnChainId": 123,
"claimedOnChainId": 123,
"kind": "mint",
"product": "UTY",
"vault": "<string>",
"direction": {
"from": "USDC",
"to": "USDC"
},
"sent": {
"value": "<string>",
"token": "USDC",
"address": "<string>",
"decimals": 123
},
"received": {
"value": "<string>",
"token": "USDC",
"address": "<string>",
"decimals": 123
},
"status": "completed",
"hash": "<string>",
"blockNumber": 123,
"timestamp": 123,
"requestId": 123,
"requestedAt": 123,
"cooldownEndsAt": 123,
"claimedAt": 123,
"claimedHash": "<string>",
"hubTx": "<string>",
"hubTimestamp": 123,
"hubBlockNumber": 123
}
]{
"error": "<string>",
"message": "<string>",
"traceId": "<string>",
"validation": [
"<string>"
]
}Path Parameters
0x-prefixed 40-character wallet address (any case).
Query Parameters
Supported: 8453 (Base), 43114 (Avalanche), 747474 (Katana)
Response
Stable composite key. Mint/deposit rows: <kind>:<chainId>:<vault>:<hash>:<eventId>. Withdrawal lifecycle rows: withdrawal:<vault>:<hubRequestId> (hub vault request id is the canonical identity for both hub-direct and composer-routed redemptions). UTY instant withdrawal rows reuse the mint/deposit format.
Chain where this activity was initiated. For hub-direct redemptions and Base mints/deposits this is 8453. For composer-routed redemptions this is the spoke chain (43114 Avalanche or 747474 Katana) derived from the composer's RedeemRequested.dst_eid. Matches the chainId query parameter on the listed row.
Chain where the claim landed. 8453 when the user redeemed directly on Base (receiver=user); the spoke chain when the composer bridged UTY back via OFT (receiver=composer, dst_eid → chainId). Null while the request is still in cooldown or claimable. For mint/deposit and UTY instant withdrawal rows this equals requestedOnChainId (atomic, no separate claim step).
Row kind. mint = UTY vault deposit (USDC → UTY). deposit = yUTY vault deposit (UTY → yUTY). withdrawal = yUTY async redemption lifecycle or UTY instant redemption.
mint, deposit, withdrawal UTY, yUTY ^0x[a-fA-F0-9]{40}$Show child attributes
Show child attributes
Input side of the swap — the token the user is giving / has given. For mint: USDC paid in. For deposit: UTY paid in. For withdrawal: shares burned (UTY for UTY-vault redemptions, yUTY for yUTY-vault redemptions). On UTY cooldown rows the value is null until the WithdrawalRequest struct is read on-chain by the API enrichment pass.
Show child attributes
Show child attributes
Output side of the swap — the token the user is receiving / has received. For mint: UTY shares minted. For deposit: yUTY shares minted. For withdrawal: asset paid out (USDC for UTY redemptions, UTY for yUTY redemptions). On in-flight withdrawal rows the value reflects the asset snapshot at request time; on claimed rows it reflects the actual settled amount.
Show child attributes
Show child attributes
Lifecycle status. completed only on mint rows. locked only on deposit rows. cooldown → claimable → claimed is the yUTY withdrawal lifecycle; UTY instant withdrawals are born at claimed.
completed, locked, cooldown, claimable, claimed Most-recent on-chain tx hash for this row. On cross-chain rows this is the spoke-side arrival; see hubTx for the hub-side leg.
^0x[a-fA-F0-9]{64}$Unix seconds of the most-recent event for this row. On withdrawal lifecycle rows this is the latest of (request, request_closed, claim) — not the original request time. See requestedAt for the request time.
Vault request id. Null on UTY instant withdrawals (no request was created). Absent on mint and deposit rows.
Unix seconds when the redemption request was created. Required on every withdrawal row, including UTY instant (where it equals claimedAt).
Unix seconds when the bonding period ends. Null on UTY instant withdrawals (no cooldown).
Unix seconds when the claim settled. Null while status is cooldown or claimable.
Tx hash of the settling Withdraw event. Null while status is cooldown or claimable.
^0x[a-fA-F0-9]{64}$Hub-side (Base) tx hash. Populated on cross-chain rows where requestedOnChainId or claimedOnChainId is a spoke (43114, 747474).
^0x[a-fA-F0-9]{64}$Unix seconds of the hub-side event. Paired with hubTx on cross-chain rows.
Hub-side block number. Paired with hubTx on cross-chain rows.