# Submit transaction This endpoint accepts transaction submissions in two formats. To submit a transaction as JSON, you must submit a SubmitTransactionRequest. To build this request, do the following: 1. Encode the transaction as BCS. If you are using a language that has native BCS support, make sure of that library. If not, you may take advantage of /transactions/encode\_submission. When using this endpoint, make sure you trust the node you're talking to, as it is possible they could manipulate your request. 2. Sign the encoded transaction and use it to create a TransactionSignature. 3. Submit the request. Make sure to use the "application/json" Content-Type. To submit a transaction as BCS, you must submit a SignedTransaction encoded as BCS. See SignedTransaction in types/src/transaction/mod.rs. Make sure to use the `application/x.aptos.signed_transaction+bcs` Content-Type. #### Request body： A request to submit a transaction **sender** string\ required A hex encoded 32 byte Aptos account address. **sequence\_number** string\ required A string containing a 64-bit unsigned integer. **max\_gas\_amount** string\ required A string containing a 64-bit unsigned integer. **gas\_unit\_price** string\ required A string containing a 64-bit unsigned integer. **expiration\_timestamp\_secs** string\ required A string containing a 64-bit unsigned integer. **payload** object required Payload which runs a single entry function, or Payload which runs a script that can run multiple functions, or An enum of the possible transaction payloads **signature** object required A single Ed25519 signature, or A Ed25519 multi-sig signature, or Multi agent signature for multi agent transactions #### **Response Header:** **X-APTOS-BLOCK-HEIGHT** integer Current block height of the chain **X-APTOS-CHAIN-ID** integer Chain ID of the current chain **X-APTOS-EPOCH** integer Current epoch of the chain **X-APTOS-LEDGER-OLDEST-VERSION** integer Oldest non-pruned ledger version of the chain **X-APTOS-LEDGER-TIMESTAMPUSEC** integer Current timestamp of the chain **X-APTOS-LEDGER-VERSION** integer Current ledger version of the chain **X-APTOS-OLDEST-BLOCK-HEIGHT** integer Oldest non-pruned block height of the chain #### **Response Body:** A transaction waiting in mempool **hash** string **sender** string\ required A hex encoded 32 byte Aptos account address. **sequence\_number** string\ required A string containing a 64-bit unsigned integer. **max\_gas\_amount** string\ required A string containing a 64-bit unsigned integer. **gas\_unit\_price** string\ required A string containing a 64-bit unsigned integer. **expiration\_timestamp\_secs** string\ required A string containing a 64-bit unsigned integer. **payload** object required Payload which runs a single entry function, or Payload which runs a script that can run multiple functions, or An enum of the possible transaction payloads **signature** object required A single Ed25519 signature, or A Ed25519 multi-sig signature, or Multi agent signature for multi agent transactions #### Example: {% code overflow="wrap" %} ```json // Request curl -X POST -H 'Content-Type: application/json' https://movement.blockpi.network/rpc/v1/your_api_key/v1/transactions --data { } // Result { } ``` {% endcode %} --- # 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://docs.blockpi.io/build/api-reference/movement/submit-transaction.md?ask= ``` 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.