Transaction History

Description

Retrieves a history of user transactions associated with a given wallet. This includes deposits, withdrawals, token transfers, claims, and other operations on Loopring DeFi.

You can filter results by transaction type using the types query parameter.

---

Endpoint

GET /api/v3/user/transactions

---

Request

Field	Type	Description	Example
address	string	(Optional) The wallet's public address. address or accountId is required.	0xbefa...b491
accountId	string	(Optional) The unique ID of the user's Loopring DeFi account. accountId or address is required.	10501
tokenSymbol	string	(Optional) The symbol of the token to filter results by (e.g., ETH , USDC ).	ETH,USDC,USDT
types	string	(Optional) Comma-separated list of transaction types to include (e.g., deposit , transfer ).	deposit,transfer
start	number	(Optional) Timestamp in milliseconds to begin the search range. -1 searches from the earliest.	-1
end	number	(Optional) Timestamp in milliseconds to end the search range. -1 returns the latest records.	-1
limit	number	(Optional) Maximum number of results to return.	6
offset	number	(Optional) Number of records to skip (used for pagination).	0

⚠️ Either address or accountId must be provided — at least one is required to query transaction history.

---

Response

Field	Type	Description	Example
totalNum	number	Total number of transactions matching the query.	1
transactions	array	A list of transaction objects. Each item contains detailed information about a single transaction.	[ ... ]
transactions[].id	number	Unique identifier for the transaction record.	6140
transactions[].txType	string	Type of transaction (e.g., TRANSFER, CHANGE_PWD, etc.).	"CHANGE_PWD"
transactions[].hash	string	Internal Loopring hash for the transaction.	"0x03ef6c84..."
transactions[].symbol	string	Symbol of the primary token involved in the transaction.	"ETH"
transactions[].amount	string	Amount of the token involved, in base units (before decimals).	"0"
transactions[].receiver	number	Receiver’s account ID. 0 if not applicable.	0
transactions[].txHash	string	Ethereum transaction hash (if applicable). Empty for off-chain actions.	""
transactions[].feeTokenSymbol	string	Token symbol used to pay transaction fees.	"ETH"
transactions[].feeAmount	string	Amount of the fee in base units.	"0"
transactions[].status	string	Transaction status (processing, processed, failed, etc.).	"processing"
transactions[].progress	string	Processing progress of the transaction.	"40%"
transactions[].timestamp	number	Time the transaction was created (in milliseconds since epoch).	1606565796033
transactions[].blockNum	number	Associated block number. 0 if not yet on-chain.	0
transactions[].updatedAt	number	Timestamp when the transaction was last updated.	1606565796128
transactions[].receiverAddress	string	Ethereum address of the receiver. May be empty if not applicable.	""
transactions[].senderAddress	string	Ethereum address of the sender.	"0x8454...4d5"
transactions[].memo	string	Optional user-provided note or memo.	""
transactions[].requestId	number	Associated request ID for reference.	923
transactions[].withdrawalInfo.recipient	string	Recipient address for the withdrawal.	""
transactions[].withdrawalInfo.fastStatus	string	Fast withdrawal status.	""
transactions[].withdrawalInfo.distributeHash	string	Hash used to track distribution status.	""
transactions[].blockIdInfo.blockId	number	ID of the block the transaction was included in.	0
transactions[].blockIdInfo.indexInBlock	number	Index of the transaction in the block.	0
transactions[].storageInfo.accountId	number	Account ID associated with the storage slot.	10905
transactions[].storageInfo.tokenId	number	Token ID associated with the transaction.	0
transactions[].storageInfo.storageId	number	Storage ID used to prevent replay attacks.	0

---

Additional Information

X-API-KEY

The X-API-KEY is required in some request headers to authenticate API calls and link them to the correct Loopring DeFi account.

You can retrieve your X-API-KEY using either of the following methods:

1. API Endpoint: Call GET /api/v3/apiKey to retrieve the API key programmatically.

2. Loopring L2 App: In the Loopring Layer 2 DApp, go to the Security section and select Export Account. The API key will be shown as apiKey.

---

Types

💡 Use the types parameter to filter only the transaction categories you care about — this can help with pagination and reduce response size.

Type	Description
change_password	A transaction that changes the user's Loopring DeFi account password.
delegated_force_withdraw	A forced withdrawal initiated by a third party on behalf of the user.
deposit	A deposit of assets from Ethereum or a Layer 2 to the user's Loopring DeFi account.
force_withdrawal	A forced withdrawal from Loopring DeFi back to Ethereum or a Layer 2 typically used when the normal withdrawal path is unavailable.
l2_staking	A transaction related to staking tokens on Loopring Layer 2.
offchain_withdrawal	A standard withdrawal request from Loopring Layer 2 to Layer 1.
send_back_lucky_token	A return of a previously received Lucky Token.
send_lucky_token	Sending a Lucky Token to another user.
transfer	A regular token transfer between two Loopring Layer 2 accounts.
unified_claim	A claim transaction that aggregates rewards (e.g., trading rebates, fee discounts).
withdraw_lucky_token	Withdrawal of a Lucky Token from Layer 2 to Layer 1.