From sgcWebSockets 4.4.8 Kraken Futures API is supported
The following APIs are supported:
WebSockets Public API: connects to a public WebSocket server.
WebSockets Private API: connects to a private WebSocket server and requires an API Key and API Secret to Authenticate against server.
REST Public API: connects to a public REST server.
REST Private API: connects to a public REST server and requires an API Key and API Secret to Authenticate against server.
Kraken Futures WebSocket Public API
Some public channels are provided without authentication. Example: you can subscribe to Ticker channel and get market data update through websocket protocol.
Kraken Futures WebSocket Private API
The subscribe and unsubscribe requests to WebSocket private feeds require a signed challenge message with the user api_secret.
The challenge is obtained as is shown in Section WebSocket API Public (using the api_key).
Authenticated requests must include both the original challenge message (original_challenge) and the signed (signed_challenge) in JSON format.
In order to get a Websockets Challenge, an API Key and API Secret must be set in Kraken Options Component, the api key provided by Kraken in your account
Example: Subscribe to AccountLog private channel.
Kraken Futures REST Public API
Use HTTP Protocol to get access to Public REST methods. Example: call GetOrderBook to get an snapshot of the Order Book of a Symbol.
Kraken Futures REST Private API
Use the REST Private API to get access to your private account, send orders, cancel orders...
This browser does not support the video element.