The REST API Gateway gives application developers everything they need to focus on their app's business logic and user experience, without getting stuck in the complexities of Ethereum transaction submission, thick Web3 client libraries, nonce management, RLP encoding, transaction signing, and smart contract management.
Just use the intuitive REST APIs generated for you, along with industry standard OpenAPI (Swagger) definitions and management APIs.
Let the REST API Gateway take care of the rest, backed by a fully-managed high throughput Apache Kafka infrastructure. Keep track of your deployed smart contracts, with descriptive names and API documentation, rather than strings of Hex addresses.
All of the complexities of submitting transactions to Ethereum are handled for you. With one click in the UI you can deploy your first smart contract, then explore that API to send transactions, and read data in a convenient web experience. No special blockchain coding expertise required.
OpenAPI (Swagger) definitions are generated for the Solidity Smart Contracts you enable on the REST API Gateway. The Blockchain becomes as simple to code against as any modern web based system. No thick client libraries needed in your app, no complex type mapping. Connect directly from your core applications, or use your existing Integration tier / Enterprise Service Bus (ESB).
The REST API Gateway handles smart contract compilation, nonce management, RLP encoding and more. It's all backed by the industry standard for reliable ordered streaming of transactions - Apache Kafka. So the same convenient APIs take you from first use, through to enterprise grade production use cases at scale.
Kaleido provides the enterprise grade connectivity your applications and back-office systems need for high throughput reliable connectivity to your on-chain smart contracts. You can submit transactions to your nodes with ease, query the data on your chain, and listen to events. We generate modern REST APIs with full OpenAPI (Swagger) documentation from your Solidity source code, with all of the methods, events and types processed – even the developer docs loaded into the definition.
For simple first use you can then perform transactions synchronously against the chain, waiting for them to complete. Then as you move towards production, use our throttling and nonce management over our Kafka backbone to stream transactions into the chain. Of course all of this is in addition to having direct JSON/RPC access to your nodes, for development of smart contract logic using Truffle, or DevOps activities with a Geth console.
Deploy and manage your Smart Contracts via our blockchain API and user interface. You upload your .sol or .zip file containing your Solidity package, and we generate you a REST API that can interact with any on-chain contract with the same Application Binary Interface (ABI).
For example, if you upload an ERC20 contract you get an interface that can query common data and submit transactions to any ERC20 based contract. You can use this generated gateway REST API to deploy new contract instances, which you know are using the same Solidity package and compiler version. e.g. each contract instance is identical. The UI and REST API of the gateway lets you manage these instances.
A REST API (Representational State Transfer API) is a type of API (Application Programming Interface) that allows communication between different systems or applications over the internet. REST APIs use HTTP (Hypertext Transfer Protocol) methods to send and receive data, and are designed to be lightweight, easy to use, and flexible.
REST APIs typically use HTTP methods such as GET, POST, PUT, DELETE, and PATCH to perform different actions. For example, the GET method is used to retrieve data from a server, while the POST method is used to send data to a server for processing.
REST APIs use a standard set of HTTP status codes to indicate the success or failure of a request. For example, a status code of 200 indicates that the request was successful, while a status code of 404 indicates that the requested resource could not be found.
REST APIs are often used to expose the data and functionality of web-based systems and services to developers, allowing them to build applications that interact with those systems and services.
REST APIs can be used in blockchain development to allow applications and services to interact with a blockchain and access its data and functionality.
For example, a blockchain-based application might use a REST API to:
By using a REST API, developers can build applications that can read data from and write data to a blockchain, as well as interact with smart contracts and other features of the blockchain.
Some blockchain platforms, such as Ethereum, provide their own built-in REST APIs that developers can use to interact with the blockchain. Other platforms, such as Bitcoin, do not have built-in REST APIs, but developers can use third-party tools or services to create their own APIs that allow access to the blockchain's data and functionality.
Overall, REST APIs are an important tool for developers building applications on top of a blockchain, as they provide a convenient and easy-to-use interface for accessing and interacting with the blockchain.
There are several benefits to using REST APIs in blockchain development:
Overall, the use of REST APIs in blockchain development can help developers build flexible, scalable, and interoperable applications that can interact with a blockchain and access its data and functionality.
REST APIs can be used by a wide range of individuals and organizations that are interested in building applications or services on top of a blockchain. Some examples of groups that might use blockchain REST APIs include:
Overall, any organization or individual that is interested in building applications or services on top of a blockchain can benefit from using REST APIs.
