Skip to main content
Currently all BFL API access is managed via individual API Accounts.

​
1. Initial Account Configuration

Primary Account Holder Setup
  • Designate a primary account holder (typically IT/Engineering lead) to create the main BFL account(s)
  • Critical: Use a company email address that will persist beyond individual employee tenure
  • Consider generic addresses like api-admin@company.com or tech@company.com
Key Generation Strategy
  • For each API account you are able to create multiple API keys
  • We currently don’t support separate usage monitoring or permissions assignment per API key
  • Monitoring and billing is specific to one respective API account

​
2. Environment Separation and Monitoring

We recommend separating environments (dev, staging, prod) via separate BFL API accounts. Currently, each will be completely independent with separate logins and no consolidated view. Benefits of Separation
  • Independent rate limits per environment
  • Clear usage analytics per environment
Recommended Setup Process
  • Create separate API accounts for each environment
  • Each environment gets dedicated API keys
  • Consider meaningful email aliases (e.g., bfl+prod@company.com, bfl+dev@company.com)
Our team is working on BFL API Organizations to address current limitations. This will enable:
  • Multiple users per organization with role-based access
  • Consolidated billing and usage views across accounts
  • Separation between personal and organization accounts
Once we introduce organizations, you will be able to migrate the individual accounts to assigned organization accounts.
⌘I