> ## 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. # Update a mention > Toggle engaged state, or update AI-judged relevance or sentiment. The `action` field selects the operation. ## OpenAPI ````yaml https://app.octolens.com/api/v2/openapi.json patch /api/v2/mentions/{sourceId} openapi: 3.1.0 info: title: Octolens API version: 2.0.0 description: >- The Octolens API lets you query mentions, manage keywords, and configure feeds programmatically. Every action available in the Octolens UI is available here. ### Authentication All v2 endpoints require an API key. Create one in **Settings > API** and pass it as `Authorization: Bearer `. Keys are scoped to the organization they were minted in; you cannot access another org's data. API keys carry a scope — `read`, `write` (implies read), or `admin` (implies write). Each endpoint documents the scope it needs via the `x-required-scope` OpenAPI extension and the scope badge in the docs surface. ### Rate limiting The v2 API is rate-limited at **500 requests per hour per organization**, across all keys for that org. The limit resets at the top of each hour (sliding hourly window). Every 2xx response carries three headers so clients can pace themselves: * `X-RateLimit-Limit` — the hourly cap (500) * `X-RateLimit-Remaining` — requests left in the current window * `X-RateLimit-Reset` — Unix timestamp (seconds) when the window resets When the cap is hit, the endpoint returns **429 Rate Limited** with an additional `Retry-After` header (seconds until the next window). The response body is the standard `ErrorResponse` with `code: "RATE_LIMITED"`. ### Error handling All non-2xx responses share the same `ErrorResponse` envelope: `{ error: { code, message, status, details? } }`. The `code` field is a stable `ApiErrorCode` enum — branch on it programmatically instead of parsing `message`. See the `ApiErrorCode` schema for the full catalog grouped by category. `VALIDATION_ERROR` (400) responses include a `details` array with per-field Zod issues — inspect `details[i].path` to pinpoint which input was rejected. ### Building filter bodies Endpoints that accept `simpleFilters` / `advancedFilters` (e.g. `POST /api/v2/mentions`, `PATCH /api/v2/feeds/{id}`) take a structured object that can be tricky to hand-craft. If you just have a natural-language description of what you want ("negative posts about pricing on reddit in the last week"), call `POST /api/v2/ai/filter-wizard` with that prompt and it will return a ready-to-use filter object you can pass straight through. servers: - url: https://app.octolens.com description: Production - url: http://localhost:3000 description: Local development security: - ApiKey: [] paths: /api/v2/mentions/{sourceId}: patch: tags: - Mentions summary: Update a mention description: >- Toggle engaged state, or update AI-judged relevance or sentiment. The `action` field selects the operation. operationId: updateMention parameters: - in: path name: sourceId schema: type: string required: true requestBody: content: application/json: schema: $ref: '#/components/schemas/UpdateMentionRequest' responses: '200': description: 200 response content: application/json: schema: type: object properties: ok: type: boolean const: true required: - ok additionalProperties: false '400': description: Validation error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Missing or invalid authentication content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: Forbidden (insufficient plan or permissions) content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '429': description: Rate limit exceeded content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: Internal server error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' components: schemas: UpdateMentionRequest: description: >- Mutation request for a mention. The `action` field discriminates which update to apply. oneOf: - type: object properties: action: description: Toggle the engaged-with flag on the mention. type: string const: engage postId: description: Internal post id. type: integer minimum: -9007199254740991 maximum: 9007199254740991 timestamp: description: >- The mention's timestamp, copied verbatim from the list/export response. Tinybird-style format (`YYYY-MM-DD HH:mm:ss.SSS`, UTC, no `Z` suffix); ISO 8601 also accepted. Used together with `sourceId` / `postId` to uniquely key the mention. example: '2026-05-06 13:35:37.000' type: string pattern: >- ^\d{4}-\d{2}-\d{2}[ T]\d{2}:\d{2}:\d{2}(\.\d{1,9})?(Z|[+-]\d{2}:?\d{2})?$ required: - action - postId - timestamp - type: object properties: action: description: Set the AI relevance score manually (user override). type: string const: relevance postId: type: integer minimum: -9007199254740991 maximum: 9007199254740991 relevance: description: 0 = high, 1 = medium, 2 = low, 3 = clear (reset). type: integer minimum: 0 maximum: 3 timestamp: description: >- The mention's timestamp, copied verbatim from the list/export response. Tinybird-style format (`YYYY-MM-DD HH:mm:ss.SSS`, UTC, no `Z` suffix); ISO 8601 also accepted. Used together with `sourceId` / `postId` to uniquely key the mention. example: '2026-05-06 13:35:37.000' type: string pattern: >- ^\d{4}-\d{2}-\d{2}[ T]\d{2}:\d{2}:\d{2}(\.\d{1,9})?(Z|[+-]\d{2}:?\d{2})?$ required: - action - postId - relevance - timestamp - type: object properties: action: description: Set the sentiment label manually (user override). type: string const: sentiment timestamp: description: >- The mention's timestamp, copied verbatim from the list/export response. Tinybird-style format (`YYYY-MM-DD HH:mm:ss.SSS`, UTC, no `Z` suffix); ISO 8601 also accepted. Used together with `sourceId` / `postId` to uniquely key the mention. example: '2026-05-06 13:35:37.000' type: string pattern: >- ^\d{4}-\d{2}-\d{2}[ T]\d{2}:\d{2}:\d{2}(\.\d{1,9})?(Z|[+-]\d{2}:?\d{2})?$ sentimentLabel: $ref: '#/components/schemas/MentionSentiment' required: - action - timestamp - sentimentLabel type: object ErrorResponse: description: >- Standard error envelope returned for all non-2xx responses. The `code` field is stable — safe to branch on programmatically. type: object properties: error: type: object properties: code: $ref: '#/components/schemas/ApiErrorCode' description: >- Machine-readable error code. See `ApiErrorCode` for the full list. example: NOT_FOUND message: description: Human-readable error message. example: Resource not found type: string status: description: HTTP status code — always matches the response status. example: 404 type: integer minimum: -9007199254740991 maximum: 9007199254740991 details: description: >- Present on `VALIDATION_ERROR` responses. Contains Zod issues describing each failing field (path, code, message). type: array items: {} required: - code - message - status additionalProperties: false required: - error additionalProperties: false MentionSentiment: description: AI-judged sentiment of the mention. example: Neutral type: string enum: - Positive - Neutral - Negative ApiErrorCode: description: >- Stable, machine-readable error code. Grouped as follows: **Auth / request shape** — `UNAUTHORIZED` (401), `FORBIDDEN` (403), `RATE_LIMITED` (429), `VALIDATION_ERROR` (400 — response carries a `details` array with Zod issues), `INTERNAL_ERROR` (500). **Not found (404)** — generic `NOT_FOUND` plus domain-specific variants: `FEED_NOT_FOUND`, `KEYWORD_NOT_FOUND`, `POST_NOT_FOUND`, `SUMMARY_NOT_FOUND`, `SUGGESTION_NOT_FOUND`, `COMPANY_NOT_FOUND`, `ORG_NOT_FOUND`, `SETTINGS_NOT_FOUND`. **Business-rule violations (400)** — `KEYWORD_LIMIT_EXCEEDED` (plan cap hit), `LAST_ADMIN` (refuses to remove the only admin), `ITEM_EXISTS` (duplicate), `INVALID_DOMAIN`, `INVALID_TIMEZONE`. type: string enum: - UNAUTHORIZED - FORBIDDEN - RATE_LIMITED - VALIDATION_ERROR - INTERNAL_ERROR - NOT_FOUND - FEED_NOT_FOUND - KEYWORD_NOT_FOUND - POST_NOT_FOUND - SUMMARY_NOT_FOUND - SUGGESTION_NOT_FOUND - COMPANY_NOT_FOUND - ORG_NOT_FOUND - SETTINGS_NOT_FOUND - KEYWORD_LIMIT_EXCEEDED - LAST_ADMIN - ITEM_EXISTS - INVALID_DOMAIN - INVALID_TIMEZONE securitySchemes: ApiKey: type: http scheme: bearer description: >- Clerk API key. Create one in Settings → API Keys. Pass as `Authorization: Bearer `. ````