Transaction Encode — Move REST API

Encode a submission-ready transaction payload.

Overview

Encodes transactions in BCS format for signing/submission.

Endpoint

POST /v1/transactions/encode_submission

Movement-Specific Notes

Use correct function/module/type arguments for entry functions.

Request

Body Schema

JSON

{ "sender": "0x...", "payload": { "type": "entry_function_payload", "function": "..." } }

Response

Success Response (200)

JSON

"0x..."

Code Examples

Bash

curl -X POST https://api-movement-mainnet.n.dwellir.com/YOUR_API_KEY/v1/transactions/encode_submission \
  -H "Content-Type: application/json" \
  -d '{"sender":"0x...","payload":{}}'

Transaction Simulation — Move REST API on Movement

Simulate Move transactions on Movement without committing. Preview gas costs, execution results, state changes, and debug errors before submitting real transactions using the Aptos-compatible REST API.

View Functions — Move REST API on Movement

Execute read-only Move view functions on Movement without submitting a transaction. Query on-chain state, token balances, pool prices, and module data using the Aptos-compatible REST API.

Transaction Encode — Move REST API

On this page