> 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/v1-es/ir-a-mainnet/api-rest.md).

# API REST

En esta sección, aprenderás cómo pasar a mainnet usando nuestra API REST

### Ponte en marcha con la API REST

Para mover tu integración REST a mainnet, actualiza **tres valores específicos de la red**.

{% hint style="warning" %}
No mezcles valores de testnet y mainnet.

Si un valor todavía apunta a testnet, la integración puede fallar.
{% endhint %}

{% stepper %}
{% step %}

### Usa el emisor del activo de mainnet

Tu activo de escrow debe usar el **dirección del emisor de mainnet**.

Si envías un emisor de activo de testnet, como USDC de testnet, no funcionará en mainnet.

Revisa las direcciones del emisor aquí:

{% content-ref url="/pages/832359f4195d68fbd217c41950b000089fc7b019" %}
[Trustlines](/trustless-work/v1-es/introduccion/stellar-and-soroban-the-backbone-of-trustless-work/trustlines.md)
{% endcontent-ref %}
{% endstep %}

{% step %}

### Cambia la URL base de la API

La URL de la API de testnet es:

`https://dev.api.trustlesswork.com`

La URL de la API de mainnet es:

`https://api.trustlesswork.com`

Asegúrate de que cada solicitud apunte a la URL de mainnet antes del lanzamiento.

Puedes verificar las URLs base aquí:

{% content-ref url="/pages/b266c4851dd58f24a9067ccb8e2c9bcf601bb61b" %}
[Introducción](/trustless-work/v1-es/api-rest/introduction.md)
{% endcontent-ref %}
{% endstep %}

{% step %}

### Genera una clave de API de mainnet

Mainnet requiere una **clave de API de mainnet**.

Una clave de API de testnet no se autenticará en la API de mainnet.

Cuando solicites la clave en la dApp, cambia primero a la pestaña de **Mainnet** .

Luego solicita y guarda la clave de forma segura.

Consulta el proceso completo aquí:

{% content-ref url="/pages/9cea75ed2a9fbec2ce588a103250c32863eb82e9" %}
[Solicitar clave de API](/trustless-work/v1-es/introduccion/developer-resources/request-api-key.md)
{% endcontent-ref %}
{% endstep %}
{% endstepper %}

### Lista de verificación de mainnet

Antes de enviar tu primera solicitud en vivo, confirma esto:

* El emisor de tu activo es el **mainnet** emisor.
* La URL base de tu API es `https://api.trustlesswork.com`.
* Tu clave de API se generó desde la pestaña **Mainnet** .
* Las wallets involucradas tienen las correctas **trustless work de mainnet**.

{% hint style="success" %}
Si estas cuatro comprobaciones pasan, tu integración REST está lista para tráfico de producción.
{% endhint %}


---

# 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/v1-es/ir-a-mainnet/api-rest.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.
