API methods available to smart contract

Docker container-based smart contracts can use node REST API. Smart contract developers can use limited list of REST API methods. This list is represented below, these methods are available directly from the container.

Addresses methods

• GET /addresses

• GET /addresses/publicKey/{publicKey}

• GET /addresses/balance/{address}

• GET /addresses/data/{address}

• GET /addresses/data/{address}/{key}

Crypto methods

• POST /crypto/encryptCommon

• POST /crypto/encryptSeparate

• POST /crypto/decrypt

Privacy methods

• GET /privacy/{policy-id}/getData/{policy-item-hash}

• GET /privacy/{policy-id}/getInfo/{policy-item-hash}

• GET /privacy/{policy-id}/hashes

• GET /privacy/{policy-id}/recipients

Transactions methods

• GET /transactions/info/{id}

• GET /transactions/address/{address}/limit/{limit}

Contracts methods

A smart contract can use Contracts methods implementing the separated /internal/contracts/ route, which is totally identical to the regular Contracts methods.

• GET /internal/contracts/{contractId}/{key}

• GET /internal/contracts/executed-tx-for/{id}

• GET /internal/contracts/{contractId}

• GET /internal/contracts

PKI methods

• PKI /verify

Docker contract authorization

A smart contract requires an authorization to use the node REST API. There are following steps for the correct REST API methods usage by the smart contract:

1. The following variables should be defined in the Docker contract environment:

• NODE_API - an URL address to the node REST API.

• API_TOKEN - an authorization token of the Docker contract.

• COMMAND - commands for the Docker contract creation and call.

• TX - a transaction which is required to the Docker contract for work (103 - 107 codes).

2. The Docker contract developer assigns the value of the variable API_TOKEN to the request header X-Contract-Api-Token. The node specifies JWT authorization token into the variable API_TOKEN for the contract creation and execution.

3. The contract code should pass the received token in the request header (X-Contract-Api-Token) each time the node API is accessed.

Was this page helpful?

Yes No