Documentation Index
Fetch the complete documentation index at: https://docs.casebender.com/llms.txt
Use this file to discover all available pages before exploring further.
CaseBender Endpoints
View the OpenAPI specification file
Authentication
All API endpoints require authentication using API keys. Include your API key in every request using one of the following methods:Recommended: Bearer Token
Include your API key as a Bearer token in theAuthorization header:
Alternative: X-Api-Key Header
You can also use theX-Api-Key header:
Creating API Keys
To create API keys:- Log in to your CaseBender instance
- Navigate to Account → API Keys
- Click Create API Key
- Configure the key name, description, tier, and scopes
- Save the key immediately - it is displayed only once and cannot be retrieved later
Using API Keys
Include the API key in all API requests:Using cURL
Using Python (requests library)
Using JavaScript/Node.js (fetch)
API Key Tiers
API keys are assigned tiers that determine rate limits:| Tier | Requests/Minute | Requests/Hour | Burst Allowance |
|---|---|---|---|
| Basic | 60 | 1,000 | 10 |
| Standard | 300 | 10,000 | 50 |
| Professional | 1,000 | 50,000 | 100 |
| Enterprise | 5,000 | 200,000 | 500 |
| Unlimited | No limit | No limit | No limit |
API Key Scopes
When creating an API key, you can limit its access to specific operations:alerts:read- Read alertsalerts:write- Create and update alertscases:read- Read casescases:write- Create and update casesobservables:read- Read observablesobservables:write- Create and update observablesusers:read- Read user informationadmin:*- Administrative operations
Common Authentication Errors
-
401 Unauthorized:
- Missing
Authorizationheader - Invalid or expired API key
- API key has been revoked or suspended
- Missing
-
403 Forbidden:
- API key lacks required scope for the operation
- TLP/PAP access restrictions
-
429 Too Many Requests:
- Rate limit exceeded for your tier
Security Best Practices
- Never share your API key - treat it like a password
- Rotate API keys regularly - revoke old keys and create new ones periodically
- Use different keys for different applications - this allows you to revoke access per application
- Set expiration dates - configure API keys to expire automatically when possible
- Use minimum required scopes - only grant the permissions your application needs