---
title: "GET /private/get_deposits"
method: GET
path: "/private/get_deposits"
tags: ["Wallet", "Private"]
---

# GET /private/get_deposits

`GET /private/get_deposits`

Retrieve the latest user deposits. Returns a list of deposit transactions with their status, amounts, addresses, confirmations, and other relevant details.

**📖 Related Article:** [Managing Deposits](https://docs.deribit.com/articles/managing-deposits-api)

**Scope:** `wallet:read`

[Try in API console](https://test.deribit.com/api_console?method=%2Fprivate%2Fget_deposits)

## Query parameters

- `currency` 'BTC' | 'ETH' | 'USDC' | 'USDT' | 'EURR', required — Currency, i.e `"BTC"`, `"ETH"`, `"USDC"`
- `count` integer
- `offset` integer

## Response `200`

Success response

- PrivateGetDepositsResponse
  - `jsonrpc` '2.0', required — The JSON-RPC version (2.0)
  - `id` integer — The id that was sent in the request
  - `result` object, required
    - `data` Deposit[], required
      - `currency` 'BTC' | 'ETH' | 'USDC' | 'USDT' | 'EURR', required — Currency, i.e `"BTC"`, `"ETH"`, `"USDC"`
      - `address` string, required — Address in proper format for currency
      - `amount` number, required — Amount of funds in given currency
      - `state` 'pending' | 'completed' | 'rejected' | 'replaced', required — Deposit state. Allowed values: <li><code>pending</code>: deposit detected on blockchain/system, compliance not yet finished</li> <li><code>completed</code>: compliance check finished successfully</li> <li><code>rejected</code>: deposit failed compliance and must be handled manually</li> <li><code>replaced</code>: deposit transaction was replaced on the blockchain and should have a new transaction hash</li>
      - `transaction_id` string, nullable, required — Transaction id in proper format for currency, `null` if id is not available
      - `source_address` string — Address in proper format for currency
      - `received_timestamp` integer, required — The timestamp (milliseconds since the Unix epoch)
      - `updated_timestamp` integer, required — The timestamp (milliseconds since the Unix epoch)
      - `note` string
      - `clearance_state` 'in_progress' | 'pending_admin_decision' | 'pending_user_input' | 'success' | 'failed' | 'cancelled' | 'refund_initiated' | 'refunded' — Clearance state indicating the current status of the transaction clearance process. Allowed values: <li><code>in_progress</code>: clearance process is in progress</li> <li><code>pending_admin_decision</code>: transaction is under manual review by Deribit admin</li> <li><code>pending_user_input</code>: user should provide additional information regarding the transaction</li> <li><code>success</code>: clearance process completed successfully</li> <li><code>failed</code>: clearance process failed, transaction is rejected</li> <li><code>cancelled</code>: transaction is cancelled (currently used only for withdrawals, meaning the withdrawal is cancelled)</li> <li><code>refund_initiated</code>: clearance process failed, transaction refund is initiated, funds are removed from Deribit balance (valid for deposits only)</li> <li><code>refunded</code>: clearance process failed, deposit amount is refunded back to the client (valid for deposits only)</li>
      - `refund_transaction_id` string, nullable — Transaction id in proper format for currency, `null` if id is not available
    - `count` integer, required — Total number of results available

---

[API](https://skmtc.net/deribit/apis/deribit-api.md) · [All operations](https://skmtc.net/deribit/apis/deribit-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/deribit/deribit-api/revisions/c254e4a8a23c/schema)