# API v1

## API key

An **API key** is a unique identifier linked to a user’s internal account. 

Issued by the **TRONEX** service, it allows users or third-party applications (such as bots or automated tools) to interact with the service directly—without using the Telegram bot.

Every API request, whether it’s checking a balance or creating a transaction order, is tied to the corresponding internal account through this key.

### How to use the API key

To authenticate, include your API key in the header of each request.

Header: **X-API-KEY**

Example:

```html
GET /api/v1/balance HTTP/1.1
Host: api.tronex.energy
X-API-KEY: YOUR_API_KEY
```

### Conclusion

An **internal account** serves as a secure space for storing and managing your assets, while an API key provides safe, automated access to that account.

For this reason, it’s essential to **keep your API key private and protect it from unauthorized use**.

### API methods:

{% content-ref url="/pages/4a68f6e0355b41ec1de3c95c109a96e32e0501bb" %}
[Balance](/docs/api-documentation/api-v1/balance.md)
{% endcontent-ref %}

{% content-ref url="/pages/f1056a6f70948ec88f22065d78939e542b393caa" %}
[Energy](/docs/api-documentation/api-v1/energy.md)
{% endcontent-ref %}

{% content-ref url="/pages/4f0dd1591a53daaf73f2a790f51dd7d8d7207f83" %}
[Bandwidth](/docs/api-documentation/api-v1/bandwidth.md)
{% endcontent-ref %}

{% content-ref url="/pages/d20bddd70e40b2112432f72704855dcf986925e9" %}
[Activation](/docs/api-documentation/api-v1/activation.md)
{% endcontent-ref %}

{% content-ref url="/pages/22a28220120cc5607452ef66fab67a975ecd7892" %}
[Orders](/docs/api-documentation/api-v1/orders.md)
{% endcontent-ref %}

<br>


---

# Agent Instructions: 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://tronex.gitbook.io/docs/api-documentation/api-v1.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.