Report Deposit

Hyperliquid

Verifies a transfer from the reported user to Notional’s Hyperliquid protocol wallet. This request requires neither a signature nor a nonce; the venue ledger supplies the deposit evidence.

Endpoint

POST /exchange

Request Body

Parameter	Type	Description
`action`*	object	Deposit-report payload

action

Field	Type	Description
`type`*	string	Must be `"reportDeposit"`
`txHash`*	string	`0x`-prefixed 32-byte Hyperliquid transaction hash (normalized to lowercase), e.g., `"0x1234567890abcdef..."`
`userAddress`*	string	User’s wallet address who executed the deposit, e.g., `"0x1111111111111111111111111111111111111111"`

Response

200: Accepted
400: Not Found

{
  "success": true,
  "txHash": "0x1234567890abcdef..."
}

{
  "error": "Deposit transaction not found on HyperLiquid for this user",
  "code": "VALIDATION_FAILED",
  "timestamp": 1785254400000
}

Response Fields

Field	Type	Description
`success`	boolean	`true` if the report was accepted for processing
`txHash`	string	Normalized transaction hash, e.g., `"0x1234567890abcdef..."`

An already-recorded deposit returns the same success shape without a second credit. Acceptance does not guarantee that the funds are available as collateral: deposit policy can put funds in segregated. Refresh Asset Balances to inspect the result. If the transfer is not yet visible in the user’s Hyperliquid ledger, the request returns 400. Retry after it appears there. Venue lookup failures return 503. For direct Polygon pUSD deposits, use Report Deposit, which requires the source user’s signed transaction-hash intent.

Start Here

Info

Analytics

Exchange

WebSocket

Endpoint

Request Body

action

Response

Response Fields

​Endpoint

​Request Body

​action

​Response

​Response Fields

Endpoint

Request Body

action

Response

Response Fields