Conformance Testing Environment

To allow clients to test their API implementation, we have a dedicated Conformance Testing Environment (CTE) publicly available that is completely separate from the production environment and does not require existing account credentials. 

In order to get started, just navigate to:
 https://conformance.cryptofacilities.com/
Click the Sign Up button and enter an e-mail and password combination to establish login credentials to CTE.
 
Please note that e-mails are disabled in this environment, therefore you do NOT need to verify the e-mail address or even have access to it. Merely note the credentials so that you may re-use them if desired.
 
Once you have signed up, you can generate a 2FA code, and then use that to generate API keys for the purpose of testing.
 
The websocket and REST API code on this environment is identical to the live production code in terms of the feeds/endpoints and the response structure.
 
To develop your implementation you can refer to the documentation here: https://support.kraken.com/hc/en-us/categories/360001456652-Futures-API
 
You may also use the Github repo which has libraries coded for multiple common programming languages: https://github.com/cryptofacilities
 
The only difference between the CTE API behaviour and that of the live production environment is that the base URL is not www.cryptofacilities.com but instead conformance.cryptofacilities.com
 

Simulation of Disorderly Market Conditions

In order to help test realistic scenarios for your API implementation, this environment has special _VOLATILE contracts which simulate disorderly market conditions so that traders who integrate their algorithms to our API can make sure they handle various scenarios elegantly.
 

Examples

On the CTE, for the websocket API you would subscribe to:
wss://conformance.cryptofacilities.com/ws/v1 
All the feeds are identical to those documented above.
 
So you could, e.g., subscribe to ticker feeds by sending: 
{  
    "event":"subscribe",
    "feed":"ticker",
    "product_ids":["PI_XBTUSD","PI_XBTUSD_VOLATILE"]
}
 
For a similar exercise on REST API you would request:
https://conformance.cryptofacilities.com/derivatives/api/v3/tickers
 
Please note that when you have successfully tested in the CTE, the base URLs in the live production platform environment works with both types: