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

# Get Annotation Reply Job Status

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

Retrieves the status of an asynchronous 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:
  title: Dify Service API
  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.
  version: 1.0.0
servers:
  - url: https://{api_base_url}
    description: >-
      Base URL of the Dify Service API. For self-hosted deployments, replace it
      with your own 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:
  - name: Chat Messages
    description: Operations related to chat messages and interactions.
  - name: Files
    description: File upload and preview operations.
  - name: End Users
    description: Operations related to end user information.
  - name: Feedback
    description: User feedback operations.
  - name: Conversations
    description: Operations related to managing conversations.
  - name: Audio
    description: Text-to-Speech and Speech-to-Text operations.
  - name: Applications
    description: Operations to retrieve application settings and information.
  - name: Annotations
    description: Operations related to managing annotations for direct replies.
  - name: Human Input
    description: Endpoints for resuming paused workflows that require human input.
  - name: Workflow Runs
    description: Operations for executing and managing workflows.
  - name: Completion Messages
    description: Operations related to text generation and completion.
  - name: Knowledge Bases
    description: >-
      Operations for managing knowledge bases, including creation,
      configuration, and retrieval.
  - name: Documents
    description: >-
      Operations for creating, updating, and managing documents within a
      knowledge base.
  - name: Chunks
    description: Operations for managing document chunks and child chunks.
  - name: Metadata
    description: >-
      Operations for managing knowledge base metadata fields and document
      metadata values.
  - name: Tags
    description: Operations for managing knowledge base tags and tag bindings.
  - name: Models
    description: Operations for retrieving available models.
  - name: Knowledge Pipeline
    description: >-
      Operations for managing and running knowledge pipelines, including
      datasource plugins and pipeline execution.
paths:
  /apps/annotation-reply/{action}/status/{job_id}:
    get:
      tags:
        - Annotations
      summary: Get Annotation Reply Job Status
      description: >-
        **Available for**: Chatflow, Chatbot, Agent apps.


        Retrieves the status of an asynchronous annotation reply configuration
        job started by [Configure Annotation
        Reply](/en/api-reference/annotations/configure-annotation-reply).
      operationId: getInitialAnnotationReplySettingsStatus
      parameters:
        - name: action
          in: path
          required: true
          description: >-
            Action type, must match the [Configure Annotation
            Reply](/en/api-reference/annotations/configure-annotation-reply)
            call.
          schema:
            type: string
            enum:
              - enable
              - disable
        - name: job_id
          in: path
          required: true
          description: >-
            Job ID returned by [Configure Annotation
            Reply](/en/api-reference/annotations/configure-annotation-reply).
          schema:
            type: string
            format: uuid
      responses:
        '200':
          description: Successfully retrieved task status.
          content:
            application/json:
              schema:
                $ref: >-
                  #/components/schemas/InitialAnnotationReplySettingsStatusResponse
              examples:
                jobStatus:
                  summary: Response Example
                  value:
                    job_id: a1b2c3d4-5678-90ab-cdef-1234567890ab
                    job_status: completed
                    error_msg: ''
        '400':
          description: '`invalid_param` : The specified job does not exist.'
          content:
            application/json:
              examples:
                invalid_param:
                  summary: invalid_param
                  value:
                    status: 400
                    code: invalid_param
                    message: The job does not exist.
components:
  schemas:
    InitialAnnotationReplySettingsStatusResponse:
      type: object
      properties:
        job_id:
          type: string
          format: uuid
          description: >-
            Job ID from the [Configure Annotation
            Reply](/en/api-reference/annotations/configure-annotation-reply)
            call.
        job_status:
          type: string
          description: >-
            Current job status. `waiting` for queued, `processing` for in
            progress, `completed` when finished, `error` if failed.
        error_msg:
          type: string
          description: >-
            Error message describing why the job failed. Empty string when
            `job_status` is not `error`.
  securitySchemes:
    ApiKeyAuth:
      type: http
      scheme: bearer
      bearerFormat: API_KEY
      description: >-
        API Key authentication. For all API requests, include your API Key in
        the `Authorization` HTTP Header, prefixed with `Bearer `. Example:
        `Authorization: Bearer {API_KEY}`. **Strongly recommend storing your API
        Key on the server-side, not shared or stored on the client-side, to
        avoid possible API-Key leakage that can lead to serious consequences.**
        Requests with a missing or invalid API key fail with HTTP `401` and
        error code `unauthorized`.

````