Accounts | Movement API Docs

Query Move account information on Movement including sequence numbers, authentication keys, and account state using the Aptos-compatible REST API.

Overview

The accounts endpoint returns core information about a Move account on Movement, including its sequence number (transaction nonce) and authentication key. This is the starting point for any account interaction: checking whether an account exists, reading its current nonce before submitting transactions, and verifying its authentication configuration.

Movement uses Aptos-compatible endpoints at /v1. Existing Aptos tooling and SDKs work with Movement by pointing the base URL to the Dwellir Movement endpoint.

Endpoint

Text

GET /v1/accounts/{address}

Base URL: https://api-movement-mainnet.n.dwellir.com/YOUR_API_KEY/v1

Code Examples

Basic Account Query

Bash

# Get account info for the framework address
curl -s "https://api-movement-mainnet.n.dwellir.com/YOUR_API_KEY/v1/accounts/0x1" \
  -H "Accept: application/json" | jq .

# Response:
# {
#   "sequence_number": "0",
#   "authentication_key": "0x0000000000000000000000000000000000000000000000000000000000000001"
# }

Get Sequence Number for Transaction Submission

Bash

# Fetch current sequence number to use as nonce
ADDR="0xYOUR_ADDRESS"
SEQ=$(curl -s "https://api-movement-mainnet.n.dwellir.com/YOUR_API_KEY/v1/accounts/$ADDR" \
  | jq -r '.sequence_number')
echo "Next sequence number to use: $SEQ"

Check if an Account Exists

Common Use Cases

Transaction Nonce Management

Before submitting a transaction, query the account to get the current sequence number. This prevents nonce conflicts and replay attacks. For applications submitting many transactions, maintain a local nonce counter and resync with the chain periodically.

Account Existence Checks

Before sending tokens to an address, verify the account exists. On Movement (like Aptos), accounts must be explicitly created by receiving an initial transfer or through the create_account function. Sending to a non-existent address will create the account automatically if using the transfer function from 0x1::aptos_account.

Authentication Key Monitoring

Track authentication key changes for security monitoring. If an account's authentication key changes unexpectedly, it may indicate a key rotation (legitimate) or compromise (security concern). Security dashboards and wallet applications should monitor this field.

Movement-Specific Notes

Use 0x-prefixed addresses. The API accepts both full 32-byte addresses and shortened forms (e.g., 0x1 is equivalent to 0x0000...0001).
Move balances are tracked as on-chain resources, not as fields on the account object. To get token balances, query the account's resources for 0x1::coin::CoinStore<CoinType>.
Account creation on Movement requires an explicit on-chain action (funding or calling create_account). A valid key pair does not automatically create an account.
The framework account 0x1 has a sequence number of "0" because it does not submit user transactions.

GET /v1/accounts/{address}/resources -- List all resources stored under an account (balances, NFTs, etc.).
GET /v1/accounts/{address}/modules -- List all Move modules published by the account.
POST /v1/transactions -- Submit a transaction (uses the sequence number from this endpoint).
GET /v1/accounts/{address}/events/{creation_number} -- Query events emitted by the account.

Accounts — Move REST API on Movement