> For the complete documentation index, see [llms.txt](https://docs.sectoral.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sectoral.xyz/developer-api/transfers.md).

# Transfer Endpoints

These endpoints let you send transfers and look them up programmatically. Just like in the app, every transfer you create here is confidential unless you say otherwise. Privacy is the starting point, not an option you have to remember to switch on.

***

## Send a transfer

```
POST /v1/transfers
```

### Body

```json
{
  "to": "string",
  "amount": "string",
  "asset": "USDG",
  "confidential": true,
  "memo": "string"
}
```

| Field          | Type      | Required | Description                                                                                      |
| -------------- | --------- | -------- | ------------------------------------------------------------------------------------------------ |
| `to`           | `string`  | Yes      | The recipient, as an `@handle` or a plain 0x address                                             |
| `amount`       | `string`  | Yes      | The amount, written as a decimal string                                                          |
| `asset`        | `string`  | No       | Defaults to `USDG`                                                                               |
| `confidential` | `boolean` | No       | Defaults to `true`. Use `false` only when the recipient wallet can't handle confidential tokens. |
| `memo`         | `string`  | No       | Stored encrypted, so only the sender and recipient can read it                                   |

### Response

```json
{
  "transfer_id": "tr_7f3a1c2d",
  "status": "confirmed",
  "to": "@vendor",
  "confidential": true,
  "tx_hash": "0x8f3ad41c9be2...7c1a",
  "created_at": "2026-07-02T14:23:09Z"
}
```

The amount you sent in the request does not come back in the response. Confidentiality applies with no exceptions: the API tells you the transfer settled, and getting the amount back means decrypting it on the client, the same as for any confidential data.

***

## Get a transfer

```
GET /v1/transfers/{transfer_id}
```

### Response

```json
{
  "transfer_id": "tr_7f3a1c2d",
  "status": "confirmed",
  "from": "@yourname",
  "to": "@vendor",
  "confidential": true,
  "tx_hash": "0x8f3ad41c9be2...7c1a",
  "created_at": "2026-07-02T14:23:09Z",
  "confirmed_at": "2026-07-02T14:23:09Z"
}
```

### Transfer statuses

| Status      | Description                                    |
| ----------- | ---------------------------------------------- |
| `pending`   | Sent to the chain and waiting for confirmation |
| `confirmed` | Finalized on-chain                             |
| `failed`    | Did not settle, so no funds changed hands      |

***

## List transfers

```
GET /v1/transfers
```

### Query parameters

| Parameter | Type      | Default | Description                                        |
| --------- | --------- | ------- | -------------------------------------------------- |
| `limit`   | `integer` | `20`    | Number of results per page, up to `100`            |
| `offset`  | `integer` | `0`     | How many results to skip for pagination            |
| `status`  | `string`  | (none)  | Return only transfers with this status             |
| `from`    | `string`  | (none)  | ISO 8601 time; returns transfers later than this   |
| `to`      | `string`  | (none)  | ISO 8601 time; returns transfers earlier than this |

***

## Error responses

| Status | Code                               | Description                                                                                                            |
| ------ | ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| `400`  | `invalid_request`                  | The body is malformed or is missing a required field                                                                   |
| `402`  | `insufficient_balance`             | The account's balance of that asset is too low                                                                         |
| `404`  | `recipient_not_found`              | That handle doesn't belong to any account                                                                              |
| `422`  | `recipient_not_confidential_ready` | The recipient's wallet can't receive confidential tokens. To send publicly instead, retry with `"confidential": false` |

***

## Full example

```bash
curl -X POST https://api.sectoral.xyz/v1/transfers \
  -H "Authorization: Bearer hc_live_xxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "@vendor",
    "amount": "125.00",
    "asset": "USDG",
    "confidential": true,
    "memo": "Invoice #4471"
  }'
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sectoral.xyz/developer-api/transfers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.