Skip to main content

Required Environment Variables

Bloom requires specific environment variables depending on your integration method:

For Direct API Integration

For MCP Server Integration

Finding Your Credentials

  1. Navigate to the Agents tab in your Bloom dashboard
  2. Find your agent in the list
  3. Copy the Agent ID from the agent details
Agent IDs are unique identifiers that look like: agent_abc123def456
  1. Go to your Profile tab in the Bloom dashboard
  2. Look for the API Keys section
  3. Copy your Organization API Key
Keep your organization API key secure. It provides access to all your organization’s resources.
For MCP servers, combine your credentials in this format:
Example:

Development vs Production

Development Environment

For local development, use a .env file:
Consider creating separate agents for development and production environments.

Production Environment

For production, set environment variables through your deployment platform:

Security Best Practices

Environment Variables

  • Never commit API keys to version control
  • Use .env files for local development
  • Rotate keys regularly in production

Agent Scopes

  • Follow principle of least privilege
  • Create specific scopes for each use case
  • Regularly audit agent permissions

Validation Script

Use this script to validate your environment setup:

Troubleshooting

Symptoms: Getting “None” values for environment variablesSolutions:
  • Ensure .env file is in the correct directory
  • Check that you’re using python-dotenv if needed
  • Verify variable names match exactly (case-sensitive)
Symptoms: 401 Unauthorized responsesSolutions:
  • Verify your organization API key is correct
  • Check that the agent ID exists and is active
  • Ensure you have the latest API key (not revoked)
Symptoms: 403 Forbidden responsesSolutions:
  • Verify agent has required scopes assigned
  • Check scope permissions include the HTTP method and path
  • Confirm integration is properly configured