Venue API Keys

Detailed instructions for venue credentials are provided below. It is recommended that you use IP Whitelisting for each venue to enhance security.

If Sub Accounts are not accessible via the Main Account API Key, users can upload individual API keys for each Sub Account.‌

Once venues are added, borrowers can verify the accuracy of their portfolio calculations on the Credora Platform Risk Dashboard. This dashboard provides an overview of the borrower's exposure and asset distribution.

Venue	API Requirements	API Input Fields	Sub Accounts
Binance	API Restrictions: Enable Reading IP Restrictions: Unrestricted (Optional Whitelist)	API Key, Secret Key	Supported by Main API Key
Bit.com	​Bind IP Address: No (Optional Whitelist) Permissions: Read	​API Key, API Secret	​Add separate API Key for Sub Accounts
Bitfinex	Account History: Get historical balances entries and trade information (on) Orders: Get orders and statuses (on) Margin Trading: Get position and margin info (on) Margin Funding: Get funding and statuses info (on) Wallets: Get wallet balances and addresses (on)	API Key, API Secret	​Add separate API Key for Sub Accounts
BitMEX	​Key Permissions: Read	​ID, Secret	​Add separate API Key for Sub Accounts
Bitstamp	General Permissions: Account balance, User transactions	Key, Secret	​Add separate API Key for Sub Accounts
Bittrex	Permissions: Read Only	API Key, Secret
Bybit	​Use the Bybit supported platforms dropdown and select X-Margin	​API Key, Private Key	​Add separate API Key for Sub Accounts
Crypto.com	Permissions: Read Only	API Secret, API Key	​Add separate API Key for Sub Accounts
Coinbase Pro	​Permissions: View	​Passphrase, API Secret, API Key	​Add separate API Key for Sub Accounts (Portfolios)
Copper	Read Only​	API Key, Secret​	​N/A
Delta Exchange	Permissions: Read Data	Key, Secret	N/A
Deribit	​Read for all fields (account, block trade, trade, wallet, custody)	​Client ID, Client Secret	​Add separate API Key for Sub Accounts
DYDX	Right click while on DYDX and select 'Inspect' Select 'Application', 'Local Storage', and then the DYDX URL. Select APIKEYPAIRS, copy required fields from the dropdown. Note your STARK Key is not required.	Key, Secret, Passphrase	N/A
Fireblocks	Request CSR (Certificate Signing Request) from Credora. Click on the avatar menu in the top right corner of the Fireblocks console. Select Settings from the dropdown menu. Click the Users tab at the top of the page. Click the Add User button in the top right corner of the page. Select API User type. Enter a user name. Select the Viewer role from the dropdown menu. Attach the CSR provided by Credora. Click Add User to submit your request.	​API Key	N/A
Gate.io	​Permission Settings: Read-only	API Key, Secret	Supported by Main API Key
Gemini	​API Key Settings: Auditor	API Key, API Secret​	​Supported by Master API Key
Huobi	​Permission Settings: Read-only	​Key, Secret	Supported by Main API Key
Kraken	​Funds: Query Funds Other: Query Ledger Entries, Access Websocket API	​API Key, Private Key	​Add separate API Key for Sub Accounts
Kraken Futures	​General API: Read Only Withdrawal API: No Access	​API Key, API Secret	​Add separate API Key for Sub Accounts
KuCoin	Permissions: Read (General)	API Key, API Secret, Passphrase	Supported by Main API Key
KuCoin Futures	Permissions: Read (General)	API Key, API Secret, Passphrase	Supported by Main API Key
OKX	​Permissions: Read	​API Key, API Secret, Passphrase	​Add separate API Key for Sub Accounts

‌