When running the node, a user interface for Swagger is available at
You use this UI to make API calls for advanced operations that are not available in the panel such as;
- Creating non-standard transactions with registers and context variables.
- Creating transactions that issue tokens.
- Creating transactions that use certain boxes as inputs.
Note that most methods in the API are protected and you would need to use your secret (that you configured earlier) to access these methods. The following images show the process of setting this secret in the Swagger UI.
Navigate to the top of the page and click the
Enter your secret in the form that pops-up as shown in the figure below.
After the password is entered and you have clicked
"Authorize", you'll see the popup below:
Now navigate to
127.0.0.1:9053/swagger#/wallet/walletAddresses in the same tab where you entered the password and click
"Try it out".
You should see the same list of addresses as you saw earlier from the panel.
An Ergo node provides a REST API accessible via HTTP. The full API specification (in OpenAPI format) is available here.
Accessing the API
Once the node is running, the API can be accessed at
To access protected API routes (such as for wallet), you must provide your secret phrase in the request headers
[api_key, Content-Type], or click the
Authorize button in swagger and enter your secret phrase there.
- /wallet/init and /wallet/restore to create a wallet (and a secret mnemonic) and restore wallet from mnemonic
- /wallet/unlock to unlock the wallet (it is unlocked after init but locked after restart)
- /wallet/lock to lock the wallet
- /wallet/payment/send to send a simple payment
- /wallet/status to get wallet status
- /wallet/deriveNextKey to derive a new key according to EIP-3 (BIP 44 implementation for Ergo)
- /wallet/balances to get wallet balance (for all the addresses)
- /wallet/transactions to get wallet transactions (for all the addresses)