> 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/v2-en/escrow-js-sdk/escrows/deployescrow.md).

# deployEscrow

Build an unsigned deploy transaction for a new single- or multi-release escrow.

Build an unsigned deploy transaction for a new v2 escrow. Returns `unsignedXdr` plus the predicted `contractId`.

### Import

```ts
import { TrustlessWorkClient } from "@trustless-work/escrow-js";
```

### Signature

```ts
client.rest.deployEscrow(
  payload: DeploySingleReleaseEscrowPayload | DeployMultiReleaseEscrowPayload,
  type: EscrowType,
  attribution?: AttributionHeaders,
): Promise<DeployEscrowResponse>
```

**Returns** `DeployEscrowResponse`: `{ unsignedXdr, txHash, contractId }`.

### Single vs multi

{% tabs %}
{% tab title="single-release" %}
`DeploySingleReleaseEscrowPayload`: `signer`, `engagementId`, `title`, `description`, `amount`, `platformFee`, `roles` (`Roles`), `milestones` (`SingleReleaseMilestonePayload[]`), `trustline` (`DeployTrustline`).

```ts
await client.rest.deployEscrow(payload, "single-release");
```

{% endtab %}

{% tab title="multi-release" %}
`DeployMultiReleaseEscrowPayload`: same fields except no top-level `amount`; `roles` is `MultiReleaseRoles`; each milestone includes `amount` + `receiver`.

```ts
await client.rest.deployEscrow(payload, "multi-release");
```

{% endtab %}
{% endtabs %}

{% hint style="info" %}
Deploy trustline shape: `{ contractId, symbol }` (Soroban SAC `C…` + asset code). Optional `attribution` maps to `X-TW-Platform` / `X-TW-Subject`.
{% endhint %}

### Example

```ts
import {
  TrustlessWorkClient,
  development,
  toTrustlessWorkError,
  TrustlessWorkApiError,
  formatApiErrorMessage,
} from "@trustless-work/escrow-js";
import type { DeploySingleReleaseEscrowPayload } from "@trustless-work/escrow-js/types";

const client = new TrustlessWorkClient({
  baseURL: development,
  apiKey: process.env.API_KEY,
});

const onDeploy = async (payload: DeploySingleReleaseEscrowPayload) => {
  try {
    const { unsignedXdr, contractId } = await client.rest.deployEscrow(
      payload,
      "single-release",
      { platformId, subjectId },
    );
    const signedXdr = await signWithWallet(unsignedXdr);
    const result = await client.rest.sendTransaction(signedXdr);
    // Prefer predicted contractId; result.contractId may also appear on confirm
    return { contractId, txHash: result.txHash };
  } catch (error: unknown) {
    const err = toTrustlessWorkError(error);
    if (err instanceof TrustlessWorkApiError) {
      console.error(formatApiErrorMessage(err));
    }
    throw error;
  }
};
```

See [Operate](/trustless-work/v2-en/escrow-js-sdk/escrows.md) and sendTransaction.


---

# 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/v2-en/escrow-js-sdk/escrows/deployescrow.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.