Skip to main content

Credentials

Credentials securely store your exchange API keys and secrets. Before connecting a trading account, you must create a credential that Cadenza uses to authenticate with the exchange on your behalf.

Overview

A Credential represents a set of API keys for a specific exchange venue. Credentials are:

  • Encrypted at rest - API secrets are never stored in plain text
  • Reusable - One credential can be used to connect multiple trading accounts
  • Verifiable - Test your API keys before connecting accounts
  • Rotatable - Update API keys without disconnecting accounts

Credential Lifecycle

┌─────────────┐     ┌─────────────┐     ┌─────────────┐
│ Create │────▶│ Verify │────▶│ Active │
│ (PENDING) │ │ (VERIFIED) │ │ (in use) │
└─────────────┘ └─────────────┘ └─────────────┘


┌─────────────┐ ┌─────────────┐
│ Revoke │◀────│ Rotate │
│ (REVOKED) │ │ (new keys) │
└─────────────┘ └─────────────┘

The Credential Object

FieldTypeDescription
credentialIdUUIDUnique identifier for the credential
venueVenueExchange venue (e.g., BINANCE, OKX, BYBIT)
credentialTypeCredentialTypeType of credential (EXCHANGE, BROKER)
nicknamestringOptional display name
statusCredentialStatusCurrent status (PENDING, VERIFIED, REVOKED)
identitiesstring[]Available trading account IDs after verification
createdAttimestampWhen the credential was created
updatedAttimestampWhen the credential was last updated

Credential Status

StatusDescription
PENDINGCredential created but not yet verified
VERIFIEDCredential verified and ready to use
FAILEDVerification failed (invalid API keys)
REVOKEDCredential has been revoked and cannot be used

Credential Type

TypeDescription
EXCHANGEDirect exchange API credentials
BROKERBroker/sub-account credentials

Supported Venues

VenueRequired FieldsAccount Types
BINANCEapiKey, apiSecretspot, margin, futures
OKXapiKey, apiSecret, apiPassphrasetrading (unified), funding
BYBITapiKey, apiSecretunified, spot, contract
COINBASEapiKey, apiSecretdefault
KRAKENapiKey, apiSecretspot, futures

See Supported Venues for detailed setup instructions for each exchange.

Next Steps

Security Best Practices

  1. Use IP Whitelisting - Restrict API keys to Cadenza's IP addresses
  2. Limit Permissions - Only enable required permissions (trade, read)
  3. Disable Withdrawals - Never enable withdrawal permissions
  4. Rotate Regularly - Update API keys periodically
  5. Monitor Usage - Review credential activity in your exchange dashboard