Endpoints for smart contract integration

We have collected articles that help you integrate your application with the rest of Partisia Platform in this section.

Connecting your application with your private deployment is possible by interacting the REST server, that reader nodes runs, while getting the updates from the block producer nodes.

The following sections explains some of the endpoints you can use to get info about the transactions and events that is executed on your private deployment. You can also get the current state of your deployed smart contracts and MPC smart contracts.

Rest endpoint examples and libraries

You can get information about blocks, transactions, contract state and more through the REST API. The REST API is also be used for sending signed transactions to the blockchain.

The REST API is available on any block producing node, you can also spin up a reader node, to minimize the load on your block producing nodes.

We also publish a number of libraries that help create transactions and using the REST API.

REST API endpoints

The endpoint to the OpenAPI is exposed by reader nodes and blockchain nodes. You can find all the different endpoints and all returned data types at http://docker:9432/openapi.

Note

To view the UI you must have a [running platform deployment](../deploy-and-operate/create-a-new-platform-deployment/),
since the nodes runs the server serving the UI.

Below is a collection of older rest endpoints that are not served from Open API server.

Transaction Information

• Get the 10 latest transactions:

  • http://docker:9432/blockchain/transaction/latest/10

• Get a specified transaction from the transaction hash:

  • http://docker:9432/blockchain/transaction/{{transactionHash}}
    • Insert the Hash of the transaction instead of {{transactionHash}}, e.g. for the transaction with the hash 95c72be12a002a4ee0f492ac10bf0da9cd32dbce396f32611b31290e80240979 the request would be http://docker:9432/blockchain/transaction/95c72be12a002a4ee0f492ac10bf0da9cd32dbce396f32611b31290e80240979

Event Information

• Get a specified event from the event hash:
  • http://localhost/blockchain/event/{{eventIdentifier}}
    • Insert the Hash of the event instead of {{eventIdentifier}}, e.g. for the event with the hash 7e3b8b053d5078af01de73f0c474fda1f9f01d97f9d850fcce0682a1431d2da2 the request would be http://docker:9432/blockchain/transaction/7e3b8b053d5078af01de73f0c474fda1f9f01d97f9d850fcce0682a1431d2da2

Block Information

• Get the block with blocknumber 1:

  • http://docker:9432/blockchain/blocks/blockTime/1

• Get the latest block number:

  • http://docker:9432/blockchain/blocks/latestBlockTime

• Get the latest block:

  • http://docker:9432/blockchain/blocks/latest

Smart Contract Information

• Get the state of a contract.
  • http://docker:9432/blockchain/contracts/04a2020bb33ef9e0323c7a3210d5cb7fd492aa0d65
    • 04a2020bb33ef9e0323c7a3210d5cb7fd492aa0d65 is the smart contract address of the MPC registry.

Account Information

• Get the info for a specified account:
  • http://docker:9432/chain/accounts/00803c974202d4dd8db22bd3833b8d123f89ea199b
    • 00803c974202d4dd8db22bd3833b8d123f89ea199b is the address of the account.

Blockchain Chain Id

• Get the id of the chain, which is used when creating transactions.
  • http://docker:9432/blockchain/chainId