GET /v1/trader/{address}/deposits-withdrawals — Transfers

GET endpoint returning a paginated, newest-first combined list of USDC deposits and withdrawals for any Polymarket wallet address.

Use this endpoint to see every USDC transfer into and out of a Polymarket wallet. It returns a single combined list — ordered newest-first — where each record’s type is either deposit or withdrawal. Use it to reconstruct a wallet’s funding history, verify that a specific transfer landed, or calculate net capital flows over time.

Request

GET https://orbscan.com/open-api/v1/trader/{address}/deposits-withdrawals

Path Parameters

address · string · required

The wallet address to query. Must be a valid Ethereum-style address.

Example: 0x43372356634781eea88d61bbdd7824cdce958882

Query Parameters

cursor · string

Pagination cursor. Pass the nextCursor value returned by the previous response to fetch the next page. Omit this parameter to start from the most recent records.

limit · integer

Number of records to return per page. Defaults to 50. Maximum is 100; values above 100 are capped automatically.

Example Request

curl

curl -G "https://orbscan.com/open-api/v1/trader/0x43372356634781eea88d61bbdd7824cdce958882/deposits-withdrawals" \
  --data-urlencode "limit=50" \
  -H "Authorization: Bearer YOUR_API_KEY"

Response

success · boolean

true when the request succeeds, false otherwise.

code · string

Application-level status code. "0" indicates success.

message · string

Human-readable status message, for example "success".

data · object

Container for the paginated results.

Show data fields

items · TransferItem[]

Array of deposit and withdrawal records, ordered newest-first.

Show TransferItem fields

txHash · string

On-chain transaction hash for this transfer.

type · string

Transfer direction. Either deposit or withdrawal.

amount · number

USDC amount transferred. The value is always positive regardless of direction; use type to determine whether funds moved in or out.

time · integer

Unix timestamp (seconds) of when the transfer occurred.

address · string

Counterparty address. For withdrawals this is the destination wallet. For deposits this is the sending address — see the note below about bridged deposits.

nextCursor · string | null

Cursor for the next page. Pass this as the cursor query parameter in your next request. null means you have reached the last page.

Example Response

{
  "success": true,
  "code": "0",
  "message": "success",
  "data": {
    "items": [
      {
        "txHash": "0x9c094e302971de8a6df70ee386bc3815597cbc24002b5f26e25c7127382efa31",
        "type": "deposit",
        "amount": 96240.383886,
        "time": 1786369038,
        "address": "0x0000000000000000000000000000000000000000"
      },
      {
        "txHash": "0xe5a5321c1486c7e11bb60b0d66cf56ba9b0c8c9e3800ac00a7e9732fc63463ab",
        "type": "withdrawal",
        "amount": 15.0,
        "time": 1786291032,
        "address": "0x4627ccd2de6c88ce2c0987f14f1d1b8e22697c23"
      }
    ],
    "nextCursor": "1786279260_1309417193"
  }
}

For bridged deposits — where funds arrive via a cross-chain bridge rather than a direct wallet transfer — the address field will be the zero address (0x0000000000000000000000000000000000000000). This is expected behavior and does not indicate an error. The first record in the example above shows exactly this case.