Skip to main content
Use Gateway transaction endpoints to simulate, send, batch, cost, and track signed MultiversX transactions.

Base URL

Responses use the MultiversX Gateway body shape: data, error, and code.

Endpoints

Transaction Fields

The Gateway does not sign transactions. Submit only transactions signed for the exact payload, nonce, sender, and chain ID.

Send Request

The JSON examples contain placeholders. Replace them with a real signed transaction before sending.

Status Request

Pass sender when available so the Gateway can route directly to the sender shard.

Edge Cases

Verify

  • Simulation returns no body-level error before sending.
  • Send response has data.txHash.
  • Status endpoint returns the expected hash status after finalization.
  • Your client handles body-level error even when HTTP status is 200.