> For the complete documentation index, see [llms.txt](https://docs.cheesecakelabs.com/stellar-plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cheesecakelabs.com/stellar-plus/reference/core/pipelines/sign-transaction.md).

# Sign Transaction

<figure><img src="/files/9kfEoxTgM1dCVeJYVKMc" alt="" width="563"><figcaption></figcaption></figure>

Given a transaction or fee bump transaction, this pipeline will verify the list of provided requirements and sign the envelope accordingly. The 'signers' array is used for the signing process, throwing an error in case a signer is missing for a given requirement.

&#x20;

{% hint style="info" %}
Soroban authorization entries are not handled by this pipeline. A  dedicated [Soroban authorization pipeline](/stellar-plus/reference/core/pipelines/sign-transaction-1.md) handles this scenario.
{% endhint %}

## Input

```typescript
type SignTransactionPipelineInput = {
  transaction: Transaction | FeeBumpTransaction
  signatureRequirements: SignatureRequirement[]
  signers: AccountHandler[]
}
```

* **transaction**: The transaction or fee bump transaction object to be signed.
* **signatureRequirements**: An array of signature requirements to be applied when signing the transaction. Refer to [Classic Signing Requirements](/stellar-plus/reference/core/pipelines/classic-signing-requirements.md) for details on how to generate the requirements.
* **signers**: Array of `AccountHandlers` for the necessary accounts to sign the transaction.

## Output

```typescript
type SignTransactionPipelineOutput = Transaction | FeeBumpTransaction
```

This pipeline directly outputs the signed transaction or fee bump transaction.


---

# 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.cheesecakelabs.com/stellar-plus/reference/core/pipelines/sign-transaction.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.