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

# Reply to tracked search result

> Queues a reply-post job through the existing tracked-search reply route.



## OpenAPI

````yaml /api-reference/openapi.json post /api/v1/platforms/{platform}/tracked-searches/{searchId}/results/{resultId}/reply
openapi: 3.1.0
info:
  title: Optareach Public API
  version: 1.0.0
  description: >-
    Platform-first API surface for accounts, prospects, campaigns, inbox,
    tracked searches, AI rooms, jobs, workspaces, analytics, billing, profile,
    and knowledge bases.
servers:
  - url: /
    description: Current environment
security: []
tags:
  - name: Meta
    description: API metadata and discovery
  - name: Platforms
    description: Platform registry and capabilities
  - name: Accounts
    description: Connected sender accounts
  - name: Prospects
    description: Prospect lists and leads
  - name: Campaigns
    description: Campaign lifecycle and performance
  - name: Inbox
    description: Conversations and messages
  - name: TrackedSearches
    description: Mentions and tracked search streams
  - name: AI
    description: AI chat rooms and enrichment
  - name: Jobs
    description: Background jobs
  - name: Workspaces
    description: Workspace management
  - name: KnowledgeBases
    description: Knowledge base management
  - name: Analytics
    description: Global dashboard metrics
  - name: Billing
    description: Subscriptions and credits
  - name: Profile
    description: Current user profile
  - name: Tags
    description: Conversation tags
  - name: Notifications
    description: Notification feed
paths:
  /api/v1/platforms/{platform}/tracked-searches/{searchId}/results/{resultId}/reply:
    post:
      tags:
        - TrackedSearches
      summary: Reply to tracked search result
      description: Queues a reply-post job through the existing tracked-search reply route.
      parameters:
        - $ref: '#/components/parameters/platform'
        - $ref: '#/components/parameters/searchId'
        - $ref: '#/components/parameters/resultId'
      requestBody:
        description: Reply payload
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ReplyRequest'
            example:
              body: We’ve helped a few founder-led teams with this exact bottleneck.
              accountId: acc_reddit_primary
      responses:
        '200':
          description: Reply queued
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    $ref: '#/components/schemas/QueuedReply'
                required:
                  - data
              example:
                data:
                  queued: true
                  jobId: job_reply_queue_123
                  resultId: result_123
        '404':
          $ref: '#/components/responses/NotFound'
components:
  parameters:
    platform:
      name: platform
      in: path
      required: true
      schema:
        type: string
    searchId:
      name: searchId
      in: path
      required: true
      schema:
        type: string
    resultId:
      name: resultId
      in: path
      required: true
      schema:
        type: string
  schemas:
    ReplyRequest:
      type: object
      properties:
        body:
          type: string
        accountId:
          type: string
      required:
        - body
    QueuedReply:
      type: object
      properties:
        queued:
          type: boolean
        jobId:
          type: string
        resultId:
          type: string
      required:
        - queued
        - jobId
        - resultId
  responses:
    NotFound:
      description: Not found
      content:
        application/json:
          schema:
            type: object
            properties:
              error:
                type: object
                properties:
                  code:
                    type: string
                  message:
                    type: string
                  details: {}
                required:
                  - code
                  - message
            required:
              - error
          example:
            error:
              code: not_found
              message: Requested resource was not found.

````