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

# Developer Guide

Start building on Trustless Work with the REST API or SDKs.

Trustless Work is **Escrow-as-a-Service** on **Stellar (Soroban)**.

Use it to deploy escrows, fund them, track milestones, and release funds. Your app drives the flow via **REST API** or **SDKs**.

{% hint style="info" %}
Most write endpoints return an **unsigned XDR**.\
You must sign it client-side with the correct **role wallet**.
{% endhint %}

### Pick your integration path

#### REST API

Use this if you want full control and you’re already signing Stellar transactions.

* [REST API: Introduction](/trustless-work/api-rest/introduction.md)

#### React SDK (hooks)

Use this if you want typed hooks for every escrow action.

* [React SDK: Getting Started](/trustless-work/escrow-react-sdk/getting-started.md)

#### Escrow Blocks SDK (UI blocks)

Use this if you want ready-made UI blocks and wallet connectivity.

* [Escrow Blocks SDK: Getting Started](/trustless-work/escrow-blocks-sdk/getting-started.md)

### Quickstart (recommended order)

{% stepper %}
{% step %}

### 1) Get access

Request an API key. You’ll need it for deploy/fund/release/dispute flows.

* [Request API Key](/trustless-work/introduction/developer-resources/request-api-key.md)
  {% endstep %}

{% step %}

### 2) Set up auth + signing

Wire up the auth header. Then get your wallet(s) ready to sign XDR.

* [Authentication](/trustless-work/introduction/developer-resources/authentication.md)
  {% endstep %}

{% step %}

### 3) Learn the data model

You’ll use these types in every request/response.

* [Schema](/trustless-work/introduction/developer-resources/schema.md)
* [Types](/trustless-work/introduction/developer-resources/types.md)
  {% endstep %}

{% step %}

### 4) Implement the core flow

Typical sequence:

1. Deploy / initialize escrow
2. Fund escrow
3. Approve or update milestones (if used)
4. Release funds (or dispute + resolve)

Use the checklist to cover edge cases and role permissions.

* [Integration checklist](/trustless-work/introduction/developer-resources/integration-checklist.md)
  {% endstep %}
  {% endstepper %}

### Prereqs (Stellar)

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

### Concepts and architecture

* [Escrow Design](/trustless-work/introduction/technology-overview.md)
* [Architecture](/trustless-work/introduction/developer-resources/architecture.md)
* [Escrow products Mix & Match Guide](/trustless-work/introduction/technology-overview/smart-escrow-design.md)

### Try the Backoffice dApp

Use it to request API keys and test flows end-to-end.

{% 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/introduction/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.