What is the best way to integrate with Request?
How to integrate Request?
The way you decide to interact with the network will determine the responsibility you have over security aspects and the settings you can adjust. Depending on your need for decentralization, you have three options:
Option A: Portal API
Easiest way to integrate Request without having to manage cryptographic keys or infrastructure, and with a fast data access.
Go to the Request Portal in order to get your API keys, and your are good to go. This is the fastest option to integrate, and also the most performant to fetch requests because the Portal caches them for you. More details in the Portal API Documentation or follow the guide.
Keep in mind that when using the Portal API, Request handles your identity's private key. Request empowers all economical actors to control their finance, and fully decentralized organizations may look for a more distributed option.
The Portal is safe to be used in small and medium sized production environments. Request Portal does not move any fund, but it's better to understand the risks
Option B: Network Client
Manage identities, encryption and network interactions yourself but let us host the Request node.
The Request Client comes as a library installed with npm. It comes with all the features needed to create, fetch and updates payment requests, including encryption capabilities. This package also comes with a development mode relying on local storage. You manage identities and private keys, which means that no other party can sign Request transactions for you or your users.
Option C: Network Node
Hosting your own node gives you full power over the Request network connections and storage options. You decide of how requests hashes are pushed to Ethereum and how to store and access details (encrypted or not).
You query the node with the same Network Client. For your test environment, you can setup a Rinkeby node or a connection with our hosted Rinkeby node (cf. Option B).