All you need to know about the APIs for Coinfloor's Trade Engine
Branch: master
Clone or download
Latest commit d220f47 Feb 22, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
AUTH.md AUTH.md: simplify and clarify Mar 27, 2018
BIST-Migration.md coinfloorex changes Feb 22, 2019
BIST.md coinfloorex changes Feb 22, 2019
EventStream.md coinfloorex changes Feb 22, 2019
IMPL-GUIDE.md IMPL-GUIDE.md: describe stochastic rounding Apr 25, 2018
LICENSE Initial commit Jan 15, 2014
LIMITS.md document REST API Jan 13, 2019
README.md coinfloorex changes Feb 22, 2019
SCALE.md Update SCALE.md Feb 6, 2019
WEBSOCKET-README.md coinfloorex changes Feb 22, 2019

README.md

Coinfloor Trade Engine APIs

Coinfloor's application programming interfaces (APIs) provide our clients programmatic access to control aspects of their accounts and to place orders on Coinfloor's trading platforms.

Coinfloor provides several APIs:

Using these interfaces, it is possible to make both authenticated and unauthenticated API calls.

Access keys are available on the Coinfloor logged-in dashboard page for verified users which, in conjunction with your account password, allow authenticated use these APIs.


General notes

To protect the performance of the system, Coinfloor imposes certain limits on the rates at which you may issue commands to the API. Please see LIMITS.md.

All quantities and prices are transmitted and received as integers with implicit scale factors. For scale information, please see SCALE.md.

Coinfloor has published client libraries for several popular languages to aid you in implementing your client application.


Getting started with the WebSocket API

The WebSocket API is accessible via WebSocket connection to the following URLs:

wss://api.coinfloor.co.uk/ (encrypted)

Commands, replies, and notifications traverse the WebSocket in text frames with JSON-formatted payloads.

We strongly recommend that you use TLS transport for all connections.

WebSocket connections to the API will time out after 60 seconds of no traffic passing in either direction. To prevent timeouts, send a Ping frame approximately every 45 seconds while the connection is otherwise idle. You do not need to send Ping frames if you are otherwise sending or receiving data frames on the socket.

Click here for more details on how to use the WebSocket API