Overview

The Contracts endpoints manage the full lifecycle of smart contracts on the Neuron platform — from proposing reusable templates to creating contract instances, sending proposals to counterparties, collecting signatures, and controlling access. Smart contracts on Neuron are XML documents that conform to the smart contract schema. They can be designed using the LegalLab application. Contracts are federated — you can sign contracts created on other Neurons through your account’s local Neuron. Signing requires a valid, approved Legal Identity and a corresponding cryptographic key.

​

Endpoints

​

Typical contract flow

​

Prerequisites

• An approved Legal Identity is required to sign contracts — see Legal identities.
• A cryptographic key must exist on the account — see Cryptography → Create key.
• All signing calls require a keyId, legalId, nonce, keySignature, and requestSignature.

​

Related

• Contracts flow guide — end-to-end walkthrough of creating and signing a contract.
• Legal identities — apply for and manage the identities used to sign contracts.
• Cryptography — create and retrieve the keys required for signing.