API Key Management
API keys provide programmatic access to the itellicoAI platform, so you can integrate agents into your applications, automate tasks, and build custom workflows. They work alongside integrations to extend your agents’ capabilities.What Are API Keys?
API keys are secure tokens that authenticate your API requests without requiring user login credentials. Key characteristics:- Account-scoped — Each key belongs to a specific account
- Permission-aware — Requests still use the account and role permissions of the key owner
- Secret — Treat like a password; never share or commit to version control
- Revocable — Can be disabled or deleted at any time
- Trackable — Monitor last used timestamp and activity
Creating API Keys
Enter a Label
Give your key a descriptive name such as:
- “Production Server”
- “Development Environment”
- “Automation System”
- “Mobile App - iOS”
Using API Keys
Authentication Header
Include your API key in theX-API-Key header:
Account Context
API keys are scoped to their account. Keys created in a parent account can access both the parent and all subaccounts.SDKs
Using the official SDKs:Managing API Keys
Viewing Keys
The API Keys page shows:| Column | Description |
|---|---|
| Label | Your descriptive name |
| Partial Key | First few characters for identification |
| Status | Active, Revoked, or Expired |
| Created | When the key was created |
| Last Used | When it was last used for an API request |
| Expires | Expiration date (if set) |
The full key is never shown after creation — only the first few characters for identification.
Editing Keys
You can update:- Label — Change the descriptive name
- Expiration date — Extend or set expiration
Revoking Keys
To temporarily disable a key without deleting it:- Go to Account → API Keys
- Find the key in the list
- Click Revoke
- The key is disabled immediately
Deleting Keys
To permanently remove a key:- Go to Account → API Keys
- Find the key and click the menu icon
- Select Delete
- Confirm deletion
Key Statuses
| Status | Description | API Access |
|---|---|---|
| Active | Key is working normally | Yes |
| Revoked | Manually disabled | No |
| Expired | Past expiration date | No |
Security Best Practices
Never Commit Keys to Version Control
Never Commit Keys to Version Control
If you accidentally commit a key:
- Revoke the key immediately
- Create a new key
- Ask your development team to remove the key from version control history.
- Deploy the new key to your applications
Use Environment Variables
Use Environment Variables
Never hardcode API keys in source code.Add
.env files to your .gitignore:One Key Per Environment
One Key Per Environment
Create separate keys for development, staging, and production. This lets you revoke a compromised key without affecting other environments.
Rotate Keys Regularly
Rotate Keys Regularly
Recommended rotation schedule:
- Production: every 90 days
- Staging: every 180 days
- Development: yearly or when team members change
- Create a new key
- Update your application with the new key
- Test thoroughly
- Revoke the old key
- Delete the old key after 30 days
Use a Secrets Manager
Use a Secrets Manager
In production, store keys in a secrets manager:
- AWS Secrets Manager
- HashiCorp Vault
- Azure Key Vault
- Google Secret Manager
- 1Password or similar team solutions
Monitor Usage
Monitor Usage
Check “Last Used” timestamps regularly. Delete keys unused for more than 90 days.
If a Key Is Compromised
Troubleshooting
401 Unauthorized
401 Unauthorized
403 Forbidden
403 Forbidden
Causes: The key owner does not have the required account permission, or the key cannot access the requested account.Solutions: Verify the account ID in the URL. Ensure the key was created in the correct account and that the creator still has the required role for the operation.
429 Too Many Requests
429 Too Many Requests
Causes: Rate limit exceeded.Solutions: Implement exponential backoff. Cache responses when possible. Spread requests over time.
FAQs
How many API keys can I create?
How many API keys can I create?
There is no hard limit. Keeping the number manageable is recommended — typically 3-5 keys for small teams, 10-15 for medium teams.
Can I use one key across multiple accounts?
Can I use one key across multiple accounts?
Keys created in a parent account can access the parent and all its subaccounts. Keys created in a subaccount can only access that subaccount.
Can subaccounts have their own API keys?
Can subaccounts have their own API keys?
Yes. Each subaccount can create independent API keys scoped to that subaccount.
Do API keys expire automatically?
Do API keys expire automatically?
Only if you set an expiration date at creation. Otherwise, keys remain active until revoked or deleted.
Next Steps
API Reference
Explore available API endpoints
SDKs
Use the official Python and TypeScript SDKs
Integrations
Connect third-party services and webhooks