> For the complete documentation index, see [llms.txt](https://teos-docs.coreledger.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://teos-docs.coreledger.net/guides/transactions/retrieve-signing-parameters-by-transaction-id.md).

# Retrieve signing parameters by transaction Id

Returns the signing parameters for a specific blockchain transaction. These parameters are required to sign the transaction using the private key of the signing address.

📘 [Learn more ](/resources/using-the-teos-api/concepts/transaction.md)about transactions.

#### Request Endpoint:

```http
GET /odata/v1.0/Transactions({key})/GetSigningParameters
```

#### Parameters

| **Parameter** | **Type**      | **Description**                                                                     | **Mandatory** |
| ------------- | ------------- | ----------------------------------------------------------------------------------- | ------------- |
| key           | string (UUID) | The unique identifier of the transaction for which signing parameters are requested | ✅             |

**Example:**

```json
91baa4d6-85af-4780-1de7-08daa77fbe04
```

#### Request Body

No request body required.

#### Response Body Example

**Media type:** `application/json`

In EVM-compatible networks (e.g., Sparknet, Ethereum, and Polygon), the "TargetAddress" is 42 characters long. In non-EVM networks, the address length may differ. For example, on Internet Computer, it is 63 characters.

```json
{
  "Amount": "string",
  "TargetAddress": "string",
  "Nonce": "string",
  "GasPrice": "string",
  "GasLimit": "string",
  "DataToSign": "string",
  "ChainId": "string"
}
```

#### Response Body Parameters:

| **Parameter** | **Type** | **Description**                                                       |
| ------------- | -------- | --------------------------------------------------------------------- |
| Amount        | string   | Amount of tokens/ethers involved in the transaction                   |
| TargetAddress | string   | Blockchain address that is the recipient or target of the transaction |
| Nonce         | string   | Transaction nonce used to prevent replay attacks                      |
| GasPrice      | string   | Gas price for the transaction in the blockchain network               |
| GasLimit      | string   | Maximum gas allowed for the transaction execution                     |
| DataToSign    | string   | The transaction payload that needs to be signed                       |
| ChainId       | string   | Blockchain chain ID where the transaction will be submitted           |

#### Responses

| **Code** | **Description**                                |
| -------- | ---------------------------------------------- |
| 200      | OK — signing parameters successfully retrieved |
| 401      | Unauthorized                                   |

<br>


---

# 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://teos-docs.coreledger.net/guides/transactions/retrieve-signing-parameters-by-transaction-id.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.