REST API as part of Credits infrastructure. Manual on how to use it on Credits blockchain.
A REST API is a way for two computer systems to communicate over HTTP in a similar way to web browsers and servers.
The term REST was introduced and defined in 2000 by Roy Fielding in his doctoral dissertation. (https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm - link to Roy Field original publication)
REST main qualities include
Client-Server. System A makes an HTTP request to a URL hosted by System B, which returns a response.
Stateless. REST is stateless: the client request should contain all the information necessary to respond to a request. In other words, it should be possible to make two or more HTTP requests in any order and the same responses will be received.
Cacheable. A response should be defined as cacheable or not.
Layered. The requesting client need not know whether it’s communicating with the actual server, a proxy, or any other intermediary.
By using a stateless protocol and standard operations, RESTful systems aim to increase the speed of performance, reliability, and the ability to grow by reusing components that can be managed and updated without affecting the system as a whole, even while it is running.
The REST API created by our team as part of Credits blockchain ecosystem takes everything into an application when a developer needs to focus on the business and user experience, without getting stuck in the complexities of transaction submission, encoding, transaction signing, and contract management.
In the simple term: REST API designed for the users to work on our blockchain without a need to build their own tool for communication. It is the interface that you can use to talk to the Credits (CS) blockchain and develop smart contracts.
To ease your work on our blockchain just use the REST APIs generated for you by the Credits team. Here is the manual!