NEM (XEM) API Documentation

NEM

NEM (XEM) is an account-based Layer 1 using Proof of Importance for block selection, with native namespaces and mosaics providing protocol-level naming and asset issuance. It does not use a general-purpose smart contract VM; full nodes process transfers and other transaction types while maintaining accounts, mosaics, namespaces, blocks, and confirmed transaction state. This protocol-native asset model makes accounts, transactions, namespaces, and mosaics the core integration primitives rather than EVM contracts or UTXO outputs.

NEM API Methods and Endpoints

NOWNodes exposes NEM's interface, plus a few others, depending on what your integration needs: its native NIS API for reading chain state and broadcasting transactions. Archive mode extends this interface to historical states and data beyond standard retention.

Browse the interfaces below for endpoint details, request parameters, response formats, and integration examples. Create an API key, select Mainnet or Testnet, choose the required interface, and start sending requests from your application.

Weighing NEM RPC providers against each other? Read the comparison guide on our blog — this page stays focused on integration reference.