> For the complete documentation index, see [llms.txt](https://docs.tronsave.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tronsave.io/developers/api-reference/buy-resources.md).

# Buy Resources

TronSave's API exposes two methods for purchasing resources (Energy and Bandwidth). Both let you estimate an order before placing it and then create the order; they differ in how the payment is authorized and settled.

| Method                                                                     | Payment authorized by                              | Settles on-chain       | Best for                                        |
| -------------------------------------------------------------------------- | -------------------------------------------------- | ---------------------- | ----------------------------------------------- |
| [Signed Transaction](/developers/api-reference/buy-resources/signed-tx.md) | Your private key signs each transaction            | Yes, per order         | Maximum control over funds; non-custodial flows |
| [API Key](/developers/api-reference/buy-resources/api-key.md)              | A TronSave API key on a prefunded internal account | No per-order chain fee | High-throughput, low-latency integrations       |

## Using Signed Transaction

You build a transaction and sign it with your own private key. The signed transaction is submitted to the blockchain network for validation and execution, so only the holder of the private key can authorize the purchase.

**Advantages**

* High security — every order is signed with your private key.
* Direct control over payment funds; you manage them yourself.

**Disadvantages**

* Transactions submitted to the blockchain network incur additional transaction fees.
* More complex to integrate — you need to handle transaction signing and validation.

Endpoints:

* [Estimate Order](/developers/api-reference/buy-resources/signed-tx/estimate-trx.md)
* [Create Order](/developers/api-reference/buy-resources/signed-tx/create-order.md)

→ [Read the Signed Transaction guide](/developers/api-reference/buy-resources/signed-tx.md)

## Using API Key

To use the API key method, create a TronSave internal account and deposit funds into it. Once the internal account exists, an API key is generated and used to authenticate your transactions — no per-order on-chain signing is required.

**Advantages**

* Fast and secure transactions.
* Easy integration.
* Saves transaction fees.

**Disadvantages**

* Funds must be deposited into the internal account before transactions can execute.
* TronSave manages the customer's internal account.

{% hint style="info" %}
Need an API key first? See [Get API Key](/developers/authentication.md).
{% endhint %}

Endpoints:

* [Estimate Order](/developers/api-reference/buy-resources/api-key/estimate-trx.md)
* [Create Order](/developers/api-reference/buy-resources/api-key/create-order.md)

→ [Read the API Key guide](/developers/api-reference/buy-resources/api-key.md)

## Next steps

* Learn the difference between [Energy and Bandwidth](/concepts/energy-and-bandwidth.md).
* Review the [Order Types](/concepts/order-types.md) before placing orders.


---

# 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:

```
GET https://docs.tronsave.io/developers/api-reference/buy-resources.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.