> For the complete documentation index, see [llms.txt](https://support.backpack.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.backpack.exchange/support-docs/cn/qian-bao/ji-shu-wen-dang/deeplinks/provider-fang-fa/signalltransactions-pi-liang-qian-ming-jiao-yi.md).

# SignAllTransactions（批量签名交易）

一旦应用建立连接，也可以一次性签名多个交易。与 [SignAndSendTransaction](/support-docs/cn/qian-bao/ji-shu-wen-dang/deeplinks/provider-fang-fa/signandsendtransaction-qian-ming-bing-fa-song-jiao-yi.md) 不同的是，Backpack 不会将这些交易提交至网络。

应用可通过 [web3.js ](https://solana-labs.github.io/solana-web3.js/classes/Connection.html#sendRawTransaction)的 `sendRawTransaction` 方法自行提交这些已签名交易。

## **基础 URL**

```
https://backpack.app/ul/v1/signAllTransactions
```

## **查询字符串参数**

* `dapp_encryption_public_key`（必填）：用于当前[connect](/support-docs/cn/qian-bao/ji-shu-wen-dang/deeplinks/provider-fang-fa/connect-lian-jie.md)（连接）会话的原始加密公钥。
* `nonce`（必填）：用于加密请求的 base58 编码随机数。
* `redirect_link`（必填）：操作完成后，Backpack 应将用户重定向至该 URI。请参阅[Specifying Redirects](/support-docs/cn/qian-bao/ji-shu-wen-dang/deeplinks/specifying-redirects-zhi-ding-zhong-ding-xiang.md)了解更多信息。需进行 URL 编码。
* `payload`（必填）：加密的 JSON 字符串，包含以下字段：

```json
{
  "transactions": [
    "...", // 序列化交易，bs58 编码
    "...", // 序列化交易，bs58 编码
  ],
  "session": "...", // 来自 connect 方法的 token
}
```

* `transactions` (必填)：一个序列化的[transactions](/support-docs/cn/qian-bao/ji-shu-wen-dang/deeplinks/provider-fang-fa/signalltransactions-pi-liang-qian-ming-jiao-yi.md)（交易）数组，Backpack 将对其进行签名，并以 base58 编码。
* `session`（必填）：从 [Connect ](/support-docs/cn/qian-bao/ji-shu-wen-dang/deeplinks/provider-fang-fa/connect-lian-jie.md)方法中接收到的会话令牌。详见[Handling Sessions](/support-docs/cn/qian-bao/ji-shu-wen-dang/deeplinks/handling-sessions-hui-hua-chu-li.md)。

## **返回值**

### Approve（同意）

* `nonce`：用于加密响应的 base58 编码随机数。
* `data`：加密的 JSON 字符串。请参考[Encryption](/support-docs/cn/qian-bao/ji-shu-wen-dang/deeplinks/encryption-jia-mi-ji-zhi.md)部分了解如何通过共享密钥解密。加密内容以 base58 编码。

```json
// 解密后的 `data` 参数内容
{
  transactions: [
      "...", // 已签名的序列化交易，bs58 编码
      "...", // 已签名的序列化交易，bs58 编码
  ] 
}
```

* **`transactions`**：一个已签名、序列化并以 base58 编码的交易数组。Backpack 不会提交这些交易。应用程序可以通过 [web3.js](https://solana-labs.github.io/solana-web3.js/classes/Connection.html#sendRawTransaction) 的 `sendRawTransaction` 方法自行提交这些交易。

### Reject（拒绝）

错误情况会以 `errorCode` 和 `errorMessage` 作为查询参数返回。

请参阅 [Errors ](/support-docs/cn/qian-bao/ji-shu-wen-dang/deeplinks/limitations-xian-zhi.md#errors-cuo-wu-chu-li)了解所有可能的错误代码。

```json
{
  "errorCode": "...",
  "errorMessage": "..."
}
```


---

# 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://support.backpack.exchange/support-docs/cn/qian-bao/ji-shu-wen-dang/deeplinks/provider-fang-fa/signalltransactions-pi-liang-qian-ming-jiao-yi.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.
