With the Octolens API, you can use data from your Octolens workspace to create custom integrations and automations. Every action available in the Octolens UI is available here. The Octolens API, MCP server, and webhooks are available on every plan.Documentation Index
Fetch the complete documentation index at: https://octolens.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
How to use the Octolens API
Create an API Key
In Octolens, navigate to Settings and then the API tab.- Click “Add new key”
- Choose a name for your API key
- Choose a scope:
read,write(implies read), oradmin(implies write) - Choose an expiration date for your API key from the dropdown
- Click Create
Quick Start
Base URL
Authentication
Bearer token in the Authorization header. Each endpoint documents the scope it requires.Rate Limits
500 requests per hour per organization (across all keys). Every 2xx response returns three headers so clients can pace themselves:X-RateLimit-Limit— the hourly cap (500)X-RateLimit-Remaining— requests left in the current windowX-RateLimit-Reset— Unix timestamp (seconds) when the window resets
Retry-After header.
Example Request
Error Handling
All non-2xx responses share the same envelope:code field is a stable ApiErrorCode enum — branch on it programmatically instead of parsing message. VALIDATION_ERROR (400) responses include a details array with per-field issues; inspect details[i].path to pinpoint which input was rejected.
Common error codes
| HTTP | Code | Meaning |
|---|---|---|
| 400 | VALIDATION_ERROR | Request body or query is malformed |
| 401 | UNAUTHORIZED | Missing or invalid API key |
| 403 | FORBIDDEN | Key lacks the required scope or permission |
| 404 | NOT_FOUND | Resource does not exist |
| 429 | RATE_LIMITED | Hourly cap hit — see Retry-After |
| 500 | INTERNAL_ERROR | Unexpected error — retry or contact support |