> For the complete documentation index, see [llms.txt](https://docs.ston.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ston.fi/developer-section/common/transaction-sending.md).

# Transaction Sending

Complete guide for sending transactions on TON blockchain - TonConnect, TON Core, and TonWeb methods

As a result of the SDK `get*TxParams` methods calls, you will get the object with the following structure

```ts
{
    to: Address;
    value: bigint;
    body?: Cell | null;
}
```

This object describes to what address the transaction should be sent and what amount of TON to pay for the gas. And `body` contains information for the contract of what action you want to perform.

Now, to actually send the transaction to the blockchain we need to use some king of sendTransaction method provided by a TON SDK you are using in your project. There is an extensive [list of TON SDKs](https://docs.ton.org/develop/dapps/apis/sdk), and everyone has a slightly different syntax for sending transactions. Usually, you can find the information about how to send the tx on each TON SDK docs, but for a few of them, we got examples right here:

* [ton](/developer-section/common/transaction-sending/toncore.md)
* [tonweb](/developer-section/common/transaction-sending/tonweb.md)
* [tonconnect](/developer-section/common/transaction-sending/tonconnect.md)


---

# 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.ston.fi/developer-section/common/transaction-sending.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.