Skip to main content

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: Include your API key as a Bearer token in the Authorization header:

Alternative: X-Api-Key Header

You can also use the X-Api-Key header:
Important: Your API key grants access to your CaseBender instance. Keep it secure and never share it publicly.

Creating API Keys

To create API keys:
  1. Log in to your CaseBender instance
  2. Navigate to AccountAPI Keys
  3. Click Create API Key
  4. Configure the key name, description, tier, and scopes
  5. Save the key immediately - it is displayed only once and cannot be retrieved later
When you create an API key, you’ll receive a single key that looks like:

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 record an intended service tier. Effective limits are enforced by the deployment and can be lower than the tier’s nominal ceiling. No tier bypasses tenant, scope, TLP, owner-status, or organization policy.

API Key Scopes

When creating an API key, you can limit its access to specific operations:
  • alerts:read - Read alerts
  • alerts:write - Create and update alerts
  • cases:read - Read cases
  • cases:write - Create and update cases
  • observables:read - Read observables
  • observables:write - Create and update observables
  • users:read - Read user information
  • Administrative scopes are shown only when the key manager already possesses the corresponding permission
The API rejects attempts to create a key with scopes or TLP clearance broader than the caller. Each key remains bound to its server-derived owner and organization.

Common Authentication Errors

  • 401 Unauthorized:
    • Missing Authorization header
    • Invalid or expired API key
    • API key has been revoked or suspended
    • API key owner has been disabled, locked, or deleted
  • 403 Forbidden:
    • API key lacks required scope for the operation
    • Organization, team, parent-object, or TLP 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
Only Authorization: Bearer and X-Api-Key are supported. Query-string credentials and split legacy key/secret headers are not accepted.