> For the complete documentation index, see [llms.txt](https://prizm.gitbook.io/pzm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prizm.gitbook.io/pzm/prizm-api/create-transaction.md).

# Create Transaction

The following API calls create PRIZM transactions using HTTP POST requests. Follow the links for examples and HTTP POST request parameters specific to each call. Refer to the sections below for [HTTP POST request parameters](/pzm/prizm-api/create-transaction.md#create-transaction-request) and [JSON response fields](/pzm/prizm-api/create-transaction.md#create-transaction-response) common to all calls that create transactions.

* [**Send Money**](/pzm/prizm-api/prizm-api-examples.md#send-money)
* [**Set Account Information**](/pzm/prizm-api/prizm-api-examples.md#set-account-info)
* [**Send Message**](/pzm/prizm-api/prizm-api-examples.md#send-message)

## Create Transaction Request

The following HTTP POST parameters are common to all API calls that create transactions:

* secretPhrase is the secret passphrase of the account (optional, but transaction neither signed nor broadcast if omitted)
* publicKey is the public key of the account (optional if secretPhrase provided)
* feeNQT is the fee (in NQT) for the transaction, 0.5% of transaction amount, from 0.05 to 10.00 PRIZM **Note:** Fee is now being calculated automatically.
* deadline is the deadline (in minutes) for the transaction to be confirmed, 32767 minutes maximum
* referencedTransactionFullHash creates a chained transaction, meaning that the current transaction cannot be confirmed unless the referenced transaction is also confirmed (optional)
* broadcast is set to false to prevent broadcasting the transaction to the network (optional)

**Note:** An optional arbitrary message can be appended to any transaction by adding message-related parameters as in [Send Message](/pzm/prizm-api/prizm-api-examples.md#send-message).

## Create Transaction Response

**The following JSON response fields are common to all API calls that create transactions:**

* signatureHash (S) is a SHA-256 hash of the transaction signature
* unsignedTransactionBytes (S) are the unsigned transaction bytes
* transactionJSON (O) is a transaction object (refer to [Get Transaction](/pzm/prizm-api/prizm-api-examples.md#get-transaction) for details)
* broadcasted (B) is true if the transaction was broadcast, false otherwise
* requestProcessingTime (N) is the API request processing time (in millisec)
* transactionBytes (S) are the signed transaction bytes
* fullHash (S) is the full hash of the signed transaction
* transaction (S) is the ID of the newly created transaction

\ <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://prizm.gitbook.io/pzm/prizm-api/create-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.