> ## Documentation Index
> Fetch the complete documentation index at: https://dify-6c0370d8-fix-template-upload-size-guidance.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Annotation Reply Job Status

> **Available for**: Chatflow, Chatbot, Legacy Agent apps.

Returns the status of an annotation reply configuration job started by [Configure Annotation Reply](/en/api-reference/annotations/configure-annotation-reply).



## OpenAPI

````yaml /en/api-reference/openapi_service.json get /apps/annotation-reply/{action}/status/{job_id}
openapi: 3.0.1
info:
  description: >-
    REST API for Dify applications and knowledge bases. Application endpoints
    authenticate with an app API key; knowledge endpoints authenticate with a
    dataset API key.
  title: Dify Service API
  version: 1.0.0
servers:
  - description: >-
      Base URL of the Dify Service API. For self-hosted deployments, replace it
      with your own API base URL.
    url: https://{api_base_url}
    variables:
      api_base_url:
        default: api.dify.ai/v1
        description: Host and path of the API base URL, without the `https://` prefix.
security:
  - ApiKeyAuth: []
tags:
  - description: Operations related to chat messages and interactions.
    name: Chat Messages
  - description: File upload and preview operations.
    name: Files
  - description: Operations related to end user information.
    name: End Users
  - description: User feedback operations.
    name: Feedback
  - description: Operations related to managing conversations.
    name: Conversations
  - description: Text-to-Speech and Speech-to-Text operations.
    name: Audio
  - description: Operations to retrieve application settings and information.
    name: Applications
  - description: Operations related to managing annotations for direct replies.
    name: Annotations
  - description: Endpoints for resuming paused workflows that require human input.
    name: Human Input
  - description: Operations for executing and managing workflows.
    name: Workflow Runs
  - description: Operations related to text generation and completion.
    name: Completion Messages
  - description: >-
      Operations for managing knowledge bases, including creation,
      configuration, and retrieval.
    name: Knowledge Bases
  - description: >-
      Operations for creating, updating, and managing documents within a
      knowledge base.
    name: Documents
  - description: Operations for managing document chunks and child chunks.
    name: Chunks
  - description: >-
      Operations for managing knowledge base metadata fields and document
      metadata values.
    name: Metadata
  - description: Operations for managing knowledge base tags and tag bindings.
    name: Tags
  - description: Operations for retrieving available models.
    name: Models
  - description: >-
      Operations for managing and running knowledge pipelines, including
      datasource plugins and pipeline execution.
    name: Knowledge Pipeline
paths:
  /apps/annotation-reply/{action}/status/{job_id}:
    get:
      tags:
        - Annotations
      summary: Get Annotation Reply Job Status
      description: >-
        **Available for**: Chatflow, Chatbot, Legacy Agent apps.


        Returns the status of an annotation reply configuration job started by
        [Configure Annotation
        Reply](/en/api-reference/annotations/configure-annotation-reply).
      operationId: getInitialAnnotationReplySettingsStatus
      parameters:
        - description: >-
            Action type, must match the [Configure Annotation
            Reply](/en/api-reference/annotations/configure-annotation-reply)
            call.
          in: path
          name: action
          required: true
          schema:
            enum:
              - enable
              - disable
            type: string
        - description: >-
            Job ID returned by [Configure Annotation
            Reply](/en/api-reference/annotations/configure-annotation-reply).
          in: path
          name: job_id
          required: true
          schema:
            format: uuid
            type: string
      responses:
        '200':
          content:
            application/json:
              examples:
                jobStatus:
                  summary: Response Example
                  value:
                    error_msg: ''
                    job_id: a1b2c3d4-5678-90ab-cdef-1234567890ab
                    job_status: completed
              schema:
                $ref: >-
                  #/components/schemas/InitialAnnotationReplySettingsStatusResponse
          description: Successfully retrieved task status.
        '400':
          content:
            application/json:
              examples:
                invalid_param:
                  summary: invalid_param
                  value:
                    code: invalid_param
                    message: The job does not exist.
                    status: 400
          description: '`invalid_param` : The specified job does not exist.'
components:
  schemas:
    InitialAnnotationReplySettingsStatusResponse:
      properties:
        error_msg:
          description: >-
            Error message describing why the job failed. Empty string when
            `job_status` is not `error`.
          type: string
        job_id:
          description: >-
            Job ID from the [Configure Annotation
            Reply](/en/api-reference/annotations/configure-annotation-reply)
            call.
          format: uuid
          type: string
        job_status:
          description: >-
            Current job status. `waiting` for queued, `processing` for in
            progress, `completed` when finished, `error` if failed.
          type: string
      type: object
  securitySchemes:
    ApiKeyAuth:
      bearerFormat: API_KEY
      description: >-
        Every request authenticates with an API key: `Authorization: Bearer
        {API_KEY}`. App endpoints take an app API key; knowledge endpoints take
        a knowledge base API key ([Get
        Started](/en/api-reference/guides/get-started)).


        Keep keys server-side; never embed them in client code. Requests with a
        missing or invalid key fail with HTTP `401` (`unauthorized`).
      scheme: bearer
      type: http

````