What Is Resfinex Token (RES)?
The Resfinex Token APIs are designed to allow access to all of the features of the Resfinex platform, subject to you complying with the API Terms of Service. The end goal is to allow users to create trading platforms on their own to create highly customized and advanced trading strategies. There are a few things that make the Resfinex API special. The Resfinex API is designed around speed – your ultimate goal is to provide your traders the fastest access to the market possible.
For this reason try to send only the required data, usually in the form of lists. Your Node.js library supports serializing of the data, if you prefer to use properties. The second feature a Web Socket user will see is the use of Snapshots. Initially, they send a full snapshot of the data. Network latency is the biggest issue for data updates. After they send the initial snapshot, they only send data updates. With those updates, the client has to update the initial data locally.
Resfinex Token Storage Key Points
|Coin Name||Resfinex Token|
|Source Code||Click Here To View Source Code|
|Explorers||Click Here To View Explorers|
|Twitter Page||Click Here To Visit Twitter Group|
|Whitepaper||Click Here To View|
|Official Project Website||Click Here To Visit Project Website|
Mission and Vision
Resfinex Token are committed to being a driving force in the blockchain revolution by increasing adoption of this innovative technology around the world. They will advance new, innovative blockchain projects that could potentially transform the way goods, services and operations are managed globally.
Resfinex Token (RES) is the heart of the Resfinex ecosystem. They have carefully designed incentive schemes to increase network effects, demand for RES, and to decrease its circulating supply. Resfinex takes a comprehensive approach to protecting your funds and information. Learn more about your security features and integrations.
Resfinex Token API access is rate limited. The rate limit applies if an IP address exceeds a certain number of requests per minute. The current limit is between 10 and 45 to a specific REST API endpoint (ie. /ticker). In case a client reaches the limit, they block the requesting IP address for 10-60 seconds on that endpoint. The API will return the JSON response. These DDoS defenses may change over time to further improve reliability.
Your security is key. For every authenticated action taken via the Resfinex API, a nonce is required. Nonces are used to guard against replay attacks. If multiple requests arrive at the API with the wrong nonce (e.g. due to an async timing issue) the API will reject the request. This means that if you want to use multiple HTTP or Web Socket connections you will need a separate API key for each client.
Two domains are utilized for REST endpoints and Web Socket channels, the difference between the two being if the request is public, or requires authentication. Do not parse text descriptions – use only codes. Text descriptions are subject to changes and adjustments without any warning.
New fields may be appended at the end of an Array or inserted in an Object without changing the API version. When change existing positional elements in an Array or existing fields in an Object, it will trigger a version change of the API.
Please use the numeric error codes that come with an error. The additional error text may change without notice. Use error codes, your application will become more reliable. Your Websocket feed lets you easily gain access to real-time market data, while your trading API lets you develop secure, programmatic trading bots.
All API keys are used at your own risk and expense. They are not responsible for any negligence, error, compromised security, malfunction, cyber attack, or other force mature affecting this environment. You hereby release, hold harmless and indemnify from any and all damages, losses or claims associated with your use of this environment. General info about the api and how it works – and your reasoning explanations on running multiple clients – an issue coming up often in the issue tracker notes section is merged with the main section.