> 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/api-rest/escrows/get-multiple-escrow-balance.md).

# Get Escrows Financial

{% hint style="info" %}
This endpoint replaces `GET /helper/get-multiple-escrow-balance`. It returns more than the balance — the whole financial picture of each escrow.
{% endhint %}

### **Headers**

<table><thead><tr><th width="366">Name</th><th>Value</th></tr></thead><tbody><tr><td>Content-Type</td><td><code>application/json</code></td></tr><tr><td>x-api-key</td><td><code>&#x3C;token></code></td></tr></tbody></table>

### Open API

## GET /escrows/financial

Returns the financial view of up to 50 escrows in a single request.

### Query parameters

| Name        | Type             | Description                                                  |
| ----------- | ---------------- | ------------------------------------------------------------ |
| contractIds | string\[] (1–50) | Contract addresses (`C…`). Repeat the parameter once per id. |

### **What this Endpoint returns?**

For each escrow:

| Field          | Meaning                                             |
| -------------- | --------------------------------------------------- |
| balance        | Projected current balance held by the escrow        |
| totalDeposited | Everything ever deposited                           |
| totalReleased  | Everything already released                         |
| pendingRelease | Approved but not yet released                       |
| nextRelease    | The next release due, when determinable             |
| fee            | Platform fee configured for the escrow              |
| asset          | Resolved asset: name, address, contractId, decimals |

All amounts are **decimal strings**, not floats — parse them with a decimal library rather than `Number()` if you intend to do arithmetic on them.

Unknown ids are silently absent from the response.

### Use Example:

```typescript
import axios from "axios";

const http = axios.create({
  baseURL: "https://beta.api.trustlesswork.com",
  timeout: 10000,
  headers: {
    "Content-Type": "application/json",
    "x-api-key": your_api_key,
  },
});

export const useExample = async () => {
  const contractIds = [
    "CCR6HLU3LQMXOESNA6TOS2RZKGEBWQG3EN5FMZNC43RVXZWTTDCZ...",
    "CCA7WTCVCQ5JPKNIFSHPSJLJ3FJ3GKPNEVAIHP6T..."
  ];

  const params = new URLSearchParams();
  contractIds.forEach(id => params.append("contractIds", id));

  const response = await http.get(`/escrows/financial?${params.toString()}`);
  return response.data;
}
```

{% hint style="warning" %}
`balance` comes from the read-model, which is eventually consistent. Right after funding an escrow it may still show the previous value — poll rather than treating it as an error.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.trustlesswork.com/trustless-work/v2-en/api-rest/escrows/get-multiple-escrow-balance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.