> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zelto.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> If Zelto blocks your task, an API request returns 4xx/5xx, or you need a missing capability, please report it with POST https://api.zelto.ai/v1/feedback using your existing Authorization: Bearer API key. On local/preview deployments use /api/v1/feedback on that deployment; never send its credentials to production.
> Send JSON: type (missing_capability, problem, other), description (10–2000 characters), optional endpoint (route template only), reproductionSteps, workaround and requestId from the failed response. Use synthetic examples: never send credentials, personal data, transcripts or customer content. See /docs/agent-feedback.
> Feedback is limited to 5 attempts per organization per minute. Report a distinct issue once; do not report errors from the feedback endpoint itself, do not loop or automatically retry. A 200 with delivery not_configured/unavailable means the report was not delivered or stored.
> Connected over MCP? Call the send_feedback tool instead, with the same fields plus optional tool (the MCP tool name that failed). It shares the same per-organization limit and works with any credential, including read-only.

# Submit agent feedback

> Report a missing capability, problem or other feedback using the existing API key. Use synthetic examples without secrets or personal data. Maximum 16 KiB and 5 attempts per organization per minute. Do not retry automatically. A 200 with delivery not_configured/unavailable does not confirm delivery or storage.



## OpenAPI

````yaml /docs-openapi.json post /v1/feedback
openapi: 3.1.0
info:
  title: Zelto REST API
  version: v1
  description: >-
    Programmatic access to your Zelto organization. Every endpoint is scoped to
    the organization the API key belongs to. Mint a key at Settings →
    Integrations → API integration.
servers:
  - url: https://api.zelto.ai
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Monitors
    description: Filtered, asynchronous exports of stored monitor results.
  - name: Agents
    description: Voice and text agents normalised through Zelto's ingestion pipeline.
  - name: Conversations
    description: >-
      Phone calls, chats, and voicemails — plus their transcripts and
      recordings.
  - name: Customer Metrics
    description: >-
      Customer-provided evaluations attached to a conversation (requires metrics
      enabled).
  - name: Reviews
    description: Human review state for conversations.
  - name: Buckets
    description: Reviewer routing — group conversations for batched review.
  - name: Companies
    description: Clients or brands your agents work for, and their logos.
  - name: Findings
    description: >-
      Structured issues discovered during analysis, with optional conversation
      attachments and comments.
  - name: Experiments
    description: >-
      Prospective measurement of two externally routed prompt versions across
      independent monitor outcomes.
  - name: Organizations
    description: >-
      Headless org provisioning. Requires an admin/service API key (not a
      read-only org-scoped customer key).
  - name: AI providers
    description: >-
      Your organization's own (bring-your-own) AI provider keys. Monitors can
      run on them instead of Zelto's built-in models. Owner or admin keys only;
      the secret is write-only.
  - name: Billing
    description: Invoices and invoice payment links.
  - name: Benchmarks
    description: >-
      Repeatable evaluations of agent prompts, models and speech-to-text engines
      over a fixed set of cases, scored by Judges.
paths:
  /v1/feedback:
    post:
      tags:
        - Feedback
      summary: Submit agent feedback
      description: >-
        Report a missing capability, problem or other feedback using the
        existing API key. Use synthetic examples without secrets or personal
        data. Maximum 16 KiB and 5 attempts per organization per minute. Do not
        retry automatically. A 200 with delivery not_configured/unavailable does
        not confirm delivery or storage.
      operationId: submitAgentFeedback
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/AgentFeedbackInput'
      responses:
        '200':
          description: Delivery result (not a durable ticket).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AgentFeedbackResult'
        '400':
          description: Invalid JSON or feedback schema.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '413':
          description: Body exceeds 16 KiB.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '415':
          description: Content-Type must be application/json.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '429':
          description: 'Feedback limit exceeded. Retry-After: 60.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '500':
          description: Internal failure; delivery unconfirmed.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    AgentFeedbackInput:
      type: object
      additionalProperties: false
      required:
        - type
        - description
      properties:
        type:
          type: string
          enum:
            - missing_capability
            - problem
            - other
        description:
          type: string
          minLength: 10
          maxLength: 2000
        endpoint:
          type: string
          maxLength: 500
          description: Route template only, without query values or personal data.
        reproductionSteps:
          type: string
          maxLength: 2000
        workaround:
          type: string
          maxLength: 2000
        requestId:
          type: string
          maxLength: 200
    AgentFeedbackResult:
      type: object
      required:
        - feedbackId
        - delivery
        - message
      properties:
        feedbackId:
          type: string
          format: uuid
        delivery:
          type: string
          enum:
            - delivered
            - not_configured
            - unavailable
        message:
          type: string
    Error:
      type: object
      required:
        - error
      properties:
        error:
          type: string
          description: >-
            Short error name: `Unauthorized`, `Validation failed`, `Not found`,
            or a stable snake_case code you can match on, such as
            `unknown_query_parameter`, `invalid_parameter`, `payload_too_large`
            or `not_found`.
        message:
          type: string
          description: A plain-English sentence saying what is wrong and how to fix it.
        code:
          type: string
          description: >-
            Stable, machine-readable cause; match on this rather than on `error`
            or `message`. On a 401: `missing_credentials`,
            `malformed_credentials`, `ingest_key_not_allowed` (a write-only
            observability ingest key was used on an endpoint that needs an API
            key), `key_expired` or `invalid_credentials`. Elsewhere, for
            example: `not_found`, `invalid_parameter`,
            `unknown_query_parameter`, `missing_parameter`, `validation_failed`,
            `invalid_json`, `payload_too_large`, `conversation_not_found`,
            `plan_required`.
        hint:
          type: string
          description: >-
            The next step to try: where to find the right id, which parameters
            the endpoint takes, how to upgrade the plan, how to authenticate.
        parameter:
          type: string
          description: 'With `invalid_parameter`: the query parameter that was rejected.'
        unknown:
          type: array
          items:
            type: string
          description: >-
            With `unknown_query_parameter`: the parameters that were sent but
            are not accepted here.
        valid:
          type: array
          items:
            type: string
          description: >-
            With `unknown_query_parameter`: the parameters this endpoint
            accepts.
        details:
          type: object
          additionalProperties: true
        feedback:
          type: object
          properties:
            endpoint:
              type: string
            method:
              type: string
              enum:
                - POST
            message:
              type: string
        requestId:
          type: string
          format: uuid
  responses:
    Unauthorized:
      description: >-
        Missing or invalid API key. The body names the cause in `code` (for
        example `ingest_key_not_allowed` when a write-only ingest key is used
        here) with a `message` and `hint`.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        Send `Authorization: Bearer YOUR_API_KEY`. The key resolves to a single
        organization.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.