> For the complete documentation index, see [llms.txt](https://docs.txn.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.txn.io/transactions/reading-crypto-deposit.md).

# Reading crypto deposit

<mark style="color:green;">`GET`</mark> `/api/public/v1/transactions/coin_deposits/:id`

Returns a single crypto deposit transaction by ID. The account transaction is returned in `data`, with its on-chain details, network, and receiving address in `included[]`.

Txn also sends each deposit as a webhook. The webhook payload has a different shape, see [Crypto deposit webhooks](https://docs.txn.io/transactions/crypto-deposit-webhooks.md).

**Headers**

| Name          | Value                      |
| ------------- | -------------------------- |
| Content-Type  | `application/vnd.api+json` |
| Authorization | `Bearer <api_key>`         |

**Path Parameters**

| Name | Type   | Description     |
| ---- | ------ | --------------- |
| id   | string | Transaction ID. |

**cURL**

```bash
curl "https://api.sandbox.txn.io/api/public/v1/transactions/coin_deposits/b576b449-6a9e-4751-b627-9edb1e91eb76" \
     -H 'Content-Type: application/vnd.api+json' \
     -H 'Authorization: Bearer <api_key>'
```

**Response**

{% tabs %}
{% tab title="HTTP 200" %}

```json
{
  "data": {
    "id": "b576b449-6a9e-4751-b627-9edb1e91eb76",
    "type": "transactions",
    "attributes": {
      "createdAt": "2026-10-29T13:31:32.942Z",
      "simplifiedState": "completed",
      "transactionType": "CoinTransaction",
      "amount": "10.000000",
      "currency": "USDT",
      "balance": "306918.220680",
      "reference": "2810-4",
      "accountId": "e289de2b-37bd-4eff-b832-f754c31a2d95"
    },
    "relationships": {
      "account": {
        "meta": {
          "included": false
        }
      },
      "transactionDetails": {
        "data": {
          "type": "coinDeposits",
          "id": "b576b449-6a9e-4751-b627-9edb1e91eb76"
        }
      },
      "author": {
        "meta": {
          "included": false
        }
      }
    }
  },
  "included": [
    {
      "id": "b576b449-6a9e-4751-b627-9edb1e91eb76",
      "type": "coinDeposits",
      "attributes": {
        "txHash": "cc32a9fb09e6225895b1df6a4eab4b904662427650cc21ab694a8884d75bbcd7",
        "currencyCode": "USDT",
        "createdAt": "2026-10-29T13:31:32.918Z",
        "state": "completed",
        "amount": "10.000000",
        "riskScore": null,
        "reference": null,
        "accountId": "e289de2b-37bd-4eff-b832-f754c31a2d95",
        "simplifiedState": "completed",
        "sourceAddresses": [
          "TTbGTMwUwA3mncLP7xqCZei1ekaNSgeAJe"
        ],
        "clusterCategory": "Exchange",
        "clusterName": "Test ENV"
      },
      "relationships": {
        "network": {
          "data": {
            "type": "network",
            "id": "8ededca3-a1cd-4b46-8c3a-14915f706ab2"
          }
        },
        "address": {
          "data": {
            "type": "addresses",
            "id": "29242407-1270-4a2f-b34e-1ace8eaf12b7"
          }
        },
        "author": {
          "meta": {
            "included": false
          }
        }
      }
    },
    {
      "id": "8ededca3-a1cd-4b46-8c3a-14915f706ab2",
      "type": "network",
      "attributes": {
        "currencyCode": "USDT",
        "name": "Tron (TRC20)",
        "code": "ttrx:usdt"
      }
    },
    {
      "id": "29242407-1270-4a2f-b34e-1ace8eaf12b7",
      "type": "addresses",
      "attributes": {
        "label": "2810-4",
        "value": "TVzgLu6RuwbV7qNY72VQFDjSg8eRC4e7yL",
        "createdAt": "2026-10-28T13:08:59.401Z"
      },
      "relationships": {
        "account": {
          "meta": {
            "included": false
          }
        },
        "network": {
          "meta": {
            "included": false
          }
        }
      }
    }
  ],
  "meta": {},
  "jsonapi": {
    "version": "1.0"
  }
}
```

{% endtab %}
{% endtabs %}

**Response Body**

<table><thead><tr><th>Name</th><th width="99">Type</th><th>Description</th></tr></thead><tbody><tr><td>data.id</td><td>string</td><td>Account transaction ID.</td></tr><tr><td>data.type</td><td>string</td><td>Entity type returned. Always <code>transactions</code>.</td></tr><tr><td>data.attributes</td><td>object</td><td>A set of account transaction attributes.</td></tr><tr><td>data.attributes.createdAt</td><td>string</td><td>Account transaction creation timestamp in UTC+0. Refer to the <a href="https://docs.txn.io/api-basics/date-and-time-format.md">Date and time format</a> page.</td></tr><tr><td>data.attributes.simplifiedState</td><td>string</td><td>Deposit status. One of <code>pending</code>, <code>on_hold</code>, <code>travel_rule_waiting</code>, <code>completed</code>, <code>rejected</code>, <code>cancelled</code>. See <a href="https://docs.txn.io/transactions/listing-transactions.md#transaction-statuses">Transaction statuses</a>.</td></tr><tr><td>data.attributes.transactionType</td><td>string</td><td>Account transaction type. Can only be <code>CoinTransaction</code>.</td></tr><tr><td>data.attributes.amount</td><td>string</td><td>Account transaction amount.</td></tr><tr><td>data.attributes.currency</td><td>string</td><td>Account transaction currency.</td></tr><tr><td>data.attributes.balance</td><td>string</td><td>Account balance immediately after Txn processed this transaction.</td></tr><tr><td>data.attributes.reference</td><td>string</td><td>Account transaction reference.</td></tr><tr><td>data.attributes.accountId</td><td>string</td><td>ID of the account the transaction belongs to.</td></tr><tr><td>data.relationships.transactionDetails</td><td>object</td><td>Link to the on-chain deposit details, returned as a <code>coinDeposits</code> entity in <code>included[]</code>.</td></tr><tr><td>included[].id</td><td>string</td><td>Transaction ID.</td></tr><tr><td>included[].type</td><td>string</td><td>Entity type returned. Always <code>coinDeposits</code>.</td></tr><tr><td>included[].attributes</td><td>object</td><td>A set of crypto transaction attributes.</td></tr><tr><td>included[].attributes.txHash</td><td>string</td><td>Crypto transaction hash.</td></tr><tr><td>included[].attributes.currencyCode</td><td>string</td><td>Crypto transaction currency.</td></tr><tr><td>included[].attributes.createdAt</td><td>string</td><td>Crypto transaction creation timestamp in UTC+0. Refer to the <a href="https://docs.txn.io/api-basics/date-and-time-format.md">Date and time format</a> page.</td></tr><tr><td>included[].attributes.state</td><td>string</td><td>Internal Txn state. Ignore this field — use <code>data.attributes.simplifiedState</code> in your implementation.</td></tr><tr><td>included[].attributes.amount</td><td>string</td><td>Crypto transaction amount.</td></tr><tr><td>included[].attributes.accountId</td><td>string</td><td>Account ID which the crypto transaction belongs to.</td></tr><tr><td>included[].attributes.reference</td><td>string</td><td>Transaction reference.</td></tr><tr><td>included[].attributes.simplifiedState</td><td>string</td><td>Deposit status. Same value as <code>data.attributes.simplifiedState</code>.</td></tr><tr><td>included[].attributes.sourceAddresses</td><td>array</td><td>Wallet address(es) the funds were sent from. Typically a single address; may contain multiple entries when the deposit arrived via a UTXO-based network (BTC, LTC, BCH, DOGE, etc.) and the sender’s wallet combined several inputs.</td></tr><tr><td>included[].attributes.riskScore</td><td>string</td><td>Risk score for the deposit's source address from on-chain analytics screening, when available. <code>null</code> if no score was returned.</td></tr><tr><td>included[].attributes.clusterCategory</td><td>string</td><td>Category of the entity the source address is attributed to by on-chain analytics, e.g. <code>Exchange</code>. <code>null</code> until screening completes.</td></tr><tr><td>included[].attributes.clusterName</td><td>string</td><td>Name of the entity the source address is attributed to. <code>null</code> until screening completes.</td></tr><tr><td>included[].type(network).attributes.name</td><td>string</td><td>Network name. E.g. <code>Tron (TRC20)</code>.</td></tr><tr><td>included[].type(network).attributes.currencyCode</td><td>string</td><td>Currency code for the network.</td></tr><tr><td>included[].type(network).attributes.code</td><td>string</td><td>Network code. E.g. <code>ttrx:usdt</code>. Refer to <a href="https://docs.txn.io/api-basics/supported-currencies.md">Supported currencies</a>.</td></tr><tr><td>included[].type(addresses).attributes.label</td><td>string</td><td>Address label.</td></tr><tr><td>included[].type(addresses).attributes.value</td><td>string</td><td>The wallet address the deposit was received at.</td></tr><tr><td>included[].type(addresses).attributes.createdAt</td><td>string</td><td>Timestamp when the address was created.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.txn.io/transactions/reading-crypto-deposit.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
