# SignTransaction

The **easiest** and **most recommended** way to send a transaction is via [SignAndSendTransaction](/provider-methods/signandsendtransaction.md). It is safer for users, and a simpler API for developers, for Broearn Wallet to submit the transaction immediately after signing it instead of relying on the application to do so.

However, it is also possible for an app to request just the signature from Broearn Wallet. Once signed, an app can submit the transaction itself .

### Query String Parameters

* ```json
  window.bw.put.signTransaction({
      "transaction": "...", // serialized transaction, base58 encoded
      "session": "...", // token received from connect-method
  })
  ```
  * `transaction` **(required)**: The transaction that Broearn wallet will sign, serialized and encoded in base58.
  * `session` **(required)**: The session token received from the [Connect](/provider-methods/connect.md) method.

### Returns

#### :white\_check\_mark: Approve

* `data`: An encrypted JSON object. 

  ```json
  // content of decrypted `data`-parameter
  {
      transaction: "...", // signed serialized transaction, base58 encoded
  }
  ```

  * `transaction`: The signed, serialized transaction that is base58 encoded. Broearn wallet will not submit this transactions. 

#### :x:Reject

An `errorCode` and `errorMessage` as query parameters. Please refer to [Errors](/errors.md) for a full list of possible error codes.

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


---

# Agent Instructions: 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:

```
GET https://wallet-docs.broearn.com/provider-methods/signtransaction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.