> 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/introduccion/developer-resources.md).

# Guía para desarrolladores

Empieza a construir en Trustless Work con la API REST o los SDK.

Trustless Work es **Escrow-as-a-Service** en **Stellar (Soroban)**.

Úsalo para desplegar escrows, financiarlos, rastrear hitos y liberar fondos. Tu aplicación controla el flujo vía **REST API** o **SDKs**.

{% hint style="info" %}
La mayoría de los endpoints de escritura devuelven un **XDR sin firmar**.\
Debes firmarlo del lado del cliente con la **wallet de rol**.
{% endhint %}

### Elige tu camino de integración

#### REST API

Usa esto si quieres control total y ya estás firmando transacciones Stellar.

* [REST API: Introducción](/trustless-work/v1-es/api-rest/introduction.md)

#### React SDK (hooks)

Usa esto si quieres hooks tipados para cada acción de escrow.

* [React SDK: Primeros pasos](/trustless-work/v1-es/escrow-react-sdk/primeros-pasos.md)

#### Escrow Blocks SDK (bloques de UI)

Usa esto si quieres bloques de UI listos y conectividad con wallets.

* [Escrow Blocks SDK: Primeros pasos](/trustless-work/v1-es/escrow-blocks-sdk/primeros-pasos.md)

### Inicio rápido (orden recomendado)

{% stepper %}
{% step %}

### 1) Obtener acceso

Solicita una clave de API. La necesitarás para los flujos de desplegar/financiar/liberar/disputar.

* [Solicitar clave API](/trustless-work/v1-es/introduccion/developer-resources/request-api-key.md)
  {% endstep %}

{% step %}

### 2) Configurar autenticación + firma

Configura el encabezado de auth. Luego prepara tu(s) wallet(s) para firmar XDR.

* [Autenticación](/trustless-work/v1-es/introduccion/developer-resources/authentication.md)
  {% endstep %}

{% step %}

### 3) Aprender el modelo de datos

Usarás estos tipos en cada petición/respuesta.

* [Esquema](/trustless-work/v1-es/introduccion/developer-resources/schema.md)
* [Tipos](/trustless-work/v1-es/introduccion/developer-resources/tipos.md)
  {% endstep %}

{% step %}

### 4) Implementar el flujo principal

Secuencia típica:

1. Desplegar / inicializar escrow
2. Financiar escrow
3. Aprobar o actualizar hitos (si se usan)
4. Liberar fondos (o disputar + resolver)

Usa la lista de verificación para cubrir casos límite y permisos de roles.

* [Lista de verificación de integración](/trustless-work/v1-es/introduccion/developer-resources/lista-de-verificacion-de-integracion.md)
  {% endstep %}
  {% endstepper %}

### Requisitos previos (Stellar)

* [Wallets Stellar](/trustless-work/v1-es/introduccion/stellar-and-soroban-the-backbone-of-trustless-work/stellar-wallets.md)
* [Trustlines](/trustless-work/v1-es/introduccion/stellar-and-soroban-the-backbone-of-trustless-work/trustlines.md)
* [Tokens de Testnet](/trustless-work/v1-es/introduccion/stellar-and-soroban-the-backbone-of-trustless-work/testnet-tokens.md)

### Conceptos y arquitectura

* [Diseño de escrow](/trustless-work/v1-es/introduccion/technology-overview.md)
* [Arquitectura](/trustless-work/v1-es/introduccion/developer-resources/arquitectura.md)
* [Guía Mix & Match de productos escrow](/trustless-work/v1-es/introduccion/technology-overview/smart-escrow-design.md)

### Prueba la dApp Backoffice

Úsala para solicitar claves API y probar flujos de extremo a extremo.

{% embed url="<https://dapp.trustlesswork.com>" %}


---

# 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/introduccion/developer-resources.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.