Overview
BoostGPT uses API keys to authenticate requests. You’ll need two pieces of information:API Key
Used to authenticate all API requests
Project ID
Identifies which project you’re working with
Getting Your Credentials
1
Create an account
Sign up at app.boostgpt.co if you haven’t already.
2
Create a project
Create a new project from your dashboard. Each project is isolated with its own bots and data.
3
Get your Project ID
Go to your project settings to find your Project ID. You can also find it at app.boostgpt.co/settings.
4
Generate an API key
Navigate to API Keys and click “Generate New Key”. Copy it immediately - you won’t be able to see it again.
Using Environment Variables
The recommended way to store your credentials is using environment variables. Create a.env file in your project root:
.env
.env to your .gitignore:
.gitignore
- ES Modules
- CommonJS
SDK Authentication
Core SDK
Router SDK
The Router SDK uses
apiKey (camelCase) while the Core SDK uses key. Both accept the same API key value.REST API Authentication
When making direct REST API calls, include your API key in theAuthorization header:
Multiple Projects
If you’re working with multiple projects, you can create separate clients:Best Practices
Never hardcode credentials
Never hardcode credentials
Always use environment variables or a secrets manager. Never commit API keys to git.
Rotate keys regularly
Rotate keys regularly
Generate new API keys periodically and revoke old ones from your dashboard.
Use separate keys per environment
Use separate keys per environment
Use different API keys for development, staging, and production.
Restrict key access
Restrict key access
Only give API keys to team members who need them. Track which keys are used where.
Managing API Keys
You can manage your API keys from the API Keys dashboard:- Generate new keys - Create additional API keys for different environments
- Revoke keys - Immediately disable compromised or unused keys
- View usage - See which keys are being used and when
Rate Limits
BoostGPT applies rate limits to ensure fair usage:Free Tier
1,000 requests per day
Paid Plans
Higher limits based on your plan
429 Too Many Requests response. Implement exponential backoff in your retry logic:
Troubleshooting
401 Unauthorized
401 Unauthorized
403 Forbidden
403 Forbidden
Your API key doesn’t have access to the requested resource. Verify you’re using the correct Project ID.
429 Too Many Requests
429 Too Many Requests
You’ve exceeded your rate limit. Implement retry logic with exponential backoff or upgrade your plan.