How to Create a Read-Only API Key on BloFin
Follow these steps to create a read-only API key to connect your BloFin account to Flicker:
Prerequisites
- An active BloFin account
- Completed email verification and 2FA setup
Step-by-Step Instructions
-
Access API Management
- Log in to your account on Blofin.com
- Click on your profile menu in the top-right corner
- Select "API" from the dropdown menu
-
Create New API Key
- Click the "Create API Key" button
- Give your API key a descriptive name (e.g., "Flicker Read-Only")
-
Set Permissions (Important)
- Only enable the "READ" permission
- Do NOT enable "Trade", "Transfer", or "Withdraw" permissions
- This ensures Flicker can only view your account information and cannot execute trades or transfers
-
Set a Passphrase
- Enter a secure passphrase for your API key
- Save this passphrase securely - you'll need it when connecting to Flicker
- The passphrase cannot be retrieved later if lost
-
Configure IP Restrictions (Optional but Recommended)
- For enhanced security, you can restrict API access to specific IP addresses
- Add Flicker's IP address:
34.175.102.17 - Note: API keys not bound to IPs will expire after 90 days
- You can whitelist up to 20 IP addresses per API key
-
Complete Verification
- Enter any required security verification codes (email/2FA)
- Click "Confirm" to create the API key
-
Save Your Credentials
- Copy and securely store:
- API Key
- Secret Key
- Passphrase
- These credentials are shown only once and cannot be retrieved later
- Copy and securely store:
-
Connect to Flicker
- Use the saved API Key, Secret Key, and Passphrase to connect your BloFin account to Flicker
Security Best Practices
- ✅ Only enable READ permission for account monitoring
- ✅ Use a strong, unique passphrase
- ✅ Store your credentials securely (password manager recommended)
- ✅ Consider binding your API key to specific IP addresses
- ❌ Never enable withdrawal permissions for third-party integrations
- ❌ Never share your API credentials with anyone
Need Help?
If you encounter any issues, please visit BloFin's API Documentation or contact Flicker support