> For the complete documentation index, see [llms.txt](https://docs.trustlesswork.com/trustless-work/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustlesswork.com/trustless-work/v2-en/escrow-react-sdk/usesendtransaction.md).

# useSendTransaction

Most Trustless Work endpoints return an unsigned transaction in XDR format. This endpoint is used to sign such unsigned transactions and send them to the Stellar network.

## useSendTransaction

Submit a **signed** transaction XDR to Core. Call this after any operate hook returns `unsignedXdr` and your wallet has signed it.

#### Import

```tsx
import { useSendTransaction } from "@trustless-work/escrow";
// or
import { useSendTransaction } from "@trustless-work/escrow/hooks/rest";
```

#### Signature

```ts
function useSendTransaction(): {
  sendTransaction: (signedXdr: string) => Promise<SendTransactionResponse>;
};
```

**Returns** `SendTransactionResponse`:

| Field         | Type                      | Notes                                                            |
| ------------- | ------------------------- | ---------------------------------------------------------------- |
| `txHash`      | `string`                  | On-chain transaction hash                                        |
| `ledger`      | `number`                  | Ledger number                                                    |
| `contractId?` | `string`                  | Present on factory deploy confirmation                           |
| `escrow?`     | `Escrow \| EscrowSummary` | Optional snapshot after submit                                   |
| `code?`       | `SendTransactionCode`     | `STELLAR_TX_SUBMITTED` or `STELLAR_TX_SUBMITTED_INDEXER_LAGGING` |
| `message?`    | `string`                  | Human-readable note                                              |

{% hint style="warning" %}
When `code` is `STELLAR_TX_SUBMITTED_INDEXER_LAGGING`, the tx is on-chain but reads may lag. Poll `useGetEscrow` until the indexer catches up.
{% endhint %}

#### Example

```tsx
import {
  useFundEscrow,
  useSendTransaction,
  toTrustlessWorkError,
  TrustlessWorkApiError,
  formatApiErrorMessage,
} from "@trustless-work/escrow";

const { fundEscrow } = useFundEscrow();
const { sendTransaction } = useSendTransaction();

const onFund = async () => {
  try {
    const { unsignedXdr } = await fundEscrow(
      { contractId, amount: 100, signer: address },
      "single-release",
    );
    const signedXdr = await signWithWallet(unsignedXdr);
    const result = await sendTransaction(signedXdr);
    console.log(result.txHash, result.code);
  } catch (error: unknown) {
    const err = toTrustlessWorkError(error);
    if (err instanceof TrustlessWorkApiError) {
      toast.error(formatApiErrorMessage(err));
    }
    throw error;
  }
};
```

See Operate for the full mutate catalog.


---

# 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.trustlesswork.com/trustless-work/v2-en/escrow-react-sdk/usesendtransaction.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.