Grant only what is needed
Review the current Bitfinex interface and API documentation, then enable only the Funding scopes the workflow actually needs. Do not enable unrelated permissions for convenience.
BITFINEX API PERMISSIONS
API permissions are part of the asset-security boundary. Know what the workflow needs and what it should never request.
A Bitfinex API connection for lending is intended to read the required Funding state and perform restricted Funding management actions. Alpha Rate does not require withdrawal permission; users should create, inspect and revoke their API key on Bitfinex.
Review the current Bitfinex interface and API documentation, then enable only the Funding scopes the workflow actually needs. Do not enable unrelated permissions for convenience.
Funding management does not require withdrawal permission. Without it, the key cannot withdraw assets to an external address.
You can revoke the API key on Bitfinex and stop the service in Alpha Rate. After revocation, confirm the connection and any pending routine action.
API keys, secrets, private keys and passwords should never be pasted into chat, URLs, issues or public documents. Alpha Rate does not request a wallet private key.
No. A Funding API key is not a wallet private key. Never provide a wallet private key.
Subsequent API requests fail and the related service flow should stop. Create a new restricted key only after reassessing the connection.
No. The Funding workflow does not require it. Keep the key at the least-privilege scope.