Public APIs for data exchange

The public APIs made available by Ontology serve as communication bridges between dApps and nodes.

The APIs provide methods that can be used to fetch data from the chain using various parameters such as user ONT ID, transaction hash, block height etc.

There are two different APIs available publicly for developers to start using:

  1. HTTP API - RPC interface, Restful interface, Websocket interface

  2. Explorer API

Both these APIs are used to fetch data from the chain, but there are slight differences between the two, described in respective sections.

Generally speaking, it is a very tedious task for developers to run and maintain a node, but also a necessity since it is required for testing before deployment on the MainNet. Thus, to make things simpler for developers, Ontology provides public test nodes all of which use the RPC, Restful and Websocket API with default ports, thereby allowing developers to test their smart contracts and business logic.

Using public nodes

All the nodes supportRPC, RESTful, and WebSocket APi calls, and use default port numbers.

HTTPS is supported on port 10334 of the Polaris TestNet node http://polaris1.ont.io and Ontology MainNet node http://dappnode1.ont.io.

Polaris TestNet

The public TestNet nodes are:

When working on the TestNet, you'll need TestNet ONG, which can be applied for here.

Ontology MainNet

The public MainNet nodes are :

A private node can also be set up on the local machine. This can be done by directly compiling and running the source code, but for the convenience of developers, Ontology provides a method to directly download and run a private node. Please follow this link to find the guide.

Follow this link to navigate to the ONT ID public API.

To find out how to deploy your own Ontology node follow this link.

Last updated