> ## Documentation Index > Fetch the complete documentation index at: https://docs.clarifeye.ai/llms.txt > Use this file to discover all available pages before exploring further. # Submit a signal > Submit a signal about the project's content: the signal text itself, plus optional `context.additional_details` with extra context for the reviewer. The signal shows up in the review UI for domain experts. ## Signal Types | Type | is_positive Value | Description | |------|-------------------|-------------| | Thumbs up | `true` | Positive signal | | Thumbs down | `false` | Negative signal | | Neutral | `null` | Neutral or no sentiment | ## OpenAPI ````yaml /api-reference/openapi-public.yaml post /projects/{project_id}/signals/ openapi: 3.0.3 info: title: Clarifeye Platform API — Public API description: > Forward-facing, supported REST API for new integrators of the Clarifeye Platform. Covers the curated public surface: authentication, knowledge management (documents), users & teams, signals, and tool execution. New integrations should target these endpoints. ## Authentication All endpoints require authentication. Include the Authorization header in every request using either format: - `Authorization: Token ` - `Authorization: Bearer ` version: 1.0.0 contact: name: Clarifeye Support servers: - url: https://eu.app.clarifeye.ai/api/v1 description: EU - url: https://us.app.clarifeye.ai/api/v1 description: US security: - BearerAuth: [] - TokenAuth: [] tags: - name: Users description: Manage users within a project - name: Invitations description: Manage project invitations - name: Documents description: Manage documents within a project - name: Signals description: Submit signals about the project's content for domain experts to review - name: Tools description: Execute configured AI tools with custom parameters - name: Interviews description: >- Assign, run and review structured interview conversations, and manage interview drafts and campaigns - name: Artifacts description: > Knowledge-store artifact catalog: list artifacts, create and edit custom artifacts, manage scope membership, read and publish versions, and configure the cohesion guide. - name: Knowledge Changelog description: Chronological log of changes to the knowledge store's artifacts. paths: /projects/{project_id}/signals/: post: tags: - Signals summary: Submit a signal description: |- Submit a signal about the project's content: the signal text itself, plus optional `context.additional_details` with extra context for the reviewer. The signal shows up in the review UI for domain experts. ## Signal Types | Type | is_positive Value | Description | |------|-------------------|-------------| | Thumbs up | `true` | Positive signal | | Thumbs down | `false` | Negative signal | | Neutral | `null` | Neutral or no sentiment | operationId: submitSignal parameters: - $ref: '#/components/parameters/ProjectId' requestBody: required: true content: application/json: schema: type: object required: - context properties: feedback: type: string description: The signal text example: We need to cover the EU refund rules in the knowledge base context: type: object additionalProperties: true properties: additional_details: type: string description: |- Optional extra context provided alongside the signal. Displayed in the review UI. is_positive: type: boolean nullable: true description: | - `true`: Positive signal (thumbs up) - `false`: Negative signal (thumbs down) - `null`: Neutral signal example: false example: feedback: We need to cover the EU refund rules in the knowledge base is_positive: false context: additional_details: >- Several customer calls last week asked about EU refunds and we had nothing to point them to. responses: '201': description: Signal submitted successfully content: application/json: schema: $ref: '#/components/schemas/Signal' example: id: 8f14e45f-ceea-467f-a8d9-23ad7f6b3a90 created_at: '2026-06-11T09:30:00Z' updated_at: '2026-06-11T09:30:00Z' given_by: id: 1b9d6bcd-bbfd-4b2d-9b5d-ab8dfbbd4bed email: expert@example.com status: to_review feedback: We need to cover the EU refund rules in the knowledge base context: additional_details: >- Several customer calls last week asked about EU refunds and we had nothing to point them to. is_positive: false '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' components: parameters: ProjectId: name: project_id in: path required: true description: UUID of the project schema: type: string format: uuid schemas: Signal: type: object properties: id: type: string format: uuid created_at: type: string format: date-time updated_at: type: string format: date-time given_by: type: object description: User who submitted the signal properties: id: type: string format: uuid email: type: string format: email status: $ref: '#/components/schemas/SignalStatus' feedback: type: string description: Signal text comment context: type: object additionalProperties: true description: Free-form context, echoed back as submitted at creation properties: additional_details: type: string description: Extra context provided alongside the signal is_positive: type: boolean nullable: true description: | - `true`: Positive signal - `false`: Negative signal - `null`: Neutral user_message: type: string description: The user message that was responded to (computed field) conversation_title: type: string description: Title of the conversation (computed field) suggested_action_type: type: string nullable: true description: Auto-generated suggested action type suggested_action_data: type: object description: Auto-generated suggested action data SignalStatus: type: string enum: - to_review - reviewed description: | - `to_review`: Signal pending review (default) - `reviewed`: Signal has been reviewed Error: type: object properties: error: type: string description: Error message example: error: User not found ValidationError: type: object additionalProperties: type: array items: type: string example: email: - This field is required. responses: BadRequest: description: Bad request - invalid parameters or request body content: application/json: schema: oneOf: - $ref: '#/components/schemas/Error' - $ref: '#/components/schemas/ValidationError' Unauthorized: description: Unauthorized - missing or invalid authentication content: application/json: schema: $ref: '#/components/schemas/Error' example: error: Authentication credentials were not provided. Forbidden: description: Forbidden - insufficient permissions content: application/json: schema: $ref: '#/components/schemas/Error' example: error: You do not have permission to perform this action. securitySchemes: BearerAuth: type: http scheme: bearer description: 'Use Authorization: Bearer ' TokenAuth: type: apiKey in: header name: Authorization description: 'Use Authorization: Token ' ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.