> For the complete documentation index, see [llms.txt](https://leather.gitbook.io/developers/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://leather.gitbook.io/developers/stacks-methods/stx_transfersip10ft.md).

# stx\_transferSip10Ft

Request a transfer of a SIP-010 fungible token to a specified recipient.

## Method name

`stx_transferSip10Ft`

Leather builds a call to the token contract's `transfer` function and attaches its own post-condition: the sender sends exactly `amount` of `asset`. The request's `postConditions` and `postConditionMode` are not applied. The transfer carries no memo.

## **Parameters**

| Parameter   | Description                                                                             | Required | Type               |
| ----------- | --------------------------------------------------------------------------------------- | -------- | ------------------ |
| `recipient` | Stacks c32-encoded address of the recipient                                             | ✅        | `string`           |
| `asset`     | Fully qualified token identifier, as `<contract address>.<contract name>::<token name>` | ✅        | `string`           |
| `amount`    | Amount in the token's smallest unit                                                     | ✅        | `number \| string` |
| `address`   | Stacks address to send from. Defaults to the active account                             | ❌        | `string`           |
| `network`   | Network identifier                                                                      | ❌        | `string`           |
| `fee`       | Transaction fee in microSTX                                                             | ❌        | `number \| string` |
| `nonce`     | Transaction nonce                                                                       | ❌        | `number \| string` |
| `sponsored` | Build a sponsored transaction                                                           | ❌        | `boolean`          |

## **Example request**

```typescript
try {
  // Request an sBTC transfer
  const response = await window.LeatherProvider.request("stx_transferSip10Ft", {
    recipient: "SP3TB3AJ0XMZ9S6CGY2CQ6R06H1Z6DJQ1SH15ZP2H",
    asset: "SM3VDXK3WZZSA84XXFKAFAF15NNZX32CTSG82JFQ4.sbtc-token::sbtc-token",
    amount: "1000", // 1,000 sats (sBTC has 8 decimals)
  });

  console.log("Response:", response);
} catch (error) {
  console.log("Request error:", error);
}
```

## Example Response

```json
{
    "jsonrpc": "2.0",
    "id": "d3f1a7b0-5e6c-4f18-92a4-8e3b9f7c5c71",
    "result": {
        "txid": "f9c2a8f1e3b1d5a7c8e2f6a9d4b3e1c7f2a5d9b8c6e4f1a3b7d2e9c5f8a1b6c3",
        "transaction": "dead...beef"
    }
}
```

When the active account is a multisig policy, the transaction is proposed to the co-signers rather than broadcast. The result then carries `status: "proposed"` and a `proposalId`, and `txid` stays empty until the co-signers complete and broadcast it.


---

# 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://leather.gitbook.io/developers/stacks-methods/stx_transfersip10ft.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.