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

# プロンプトを取得

> 1つのプロンプトの日次推移、上位ソース、最近のスコア付き回答を取得します。



## OpenAPI

````yaml GET /v1/monitors/{id}/prompt
openapi: 3.1.0
info:
  title: querying.ai
  description: >-
    One API for every AI answer engine. Every task is asynchronous: submit, then
    collect the result via webhook or polling.
  version: 1.0.0
servers:
  - url: https://api.querying.ai
    description: Production
security:
  - bearerAuth: []
paths:
  /v1/monitors/{id}/prompt:
    get:
      tags:
        - Monitors
      summary: Get one prompt
      description: >-
        Drill into a single prompt: its per-day per-engine series, its top
        domains and pages (12 and 20, uncursored), and up to 100 recent scored
        rows. The same queries as the monitor level with one more predicate, so
        the prompt view and the monitor view cannot disagree. A prompt removed
        by a later edit stays queryable.
      operationId: getMonitorPrompt
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
        - name: prompt
          in: query
          required: true
          schema:
            type: string
            maxLength: 2000
        - name: days
          in: query
          required: false
          schema:
            type: integer
            enum:
              - 7
              - 30
              - 90
            default: 30
      responses:
        '200':
          description: Series, sources and recent rows for one prompt.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MonitorPromptResponse'
        '400':
          $ref: '#/components/responses/ValidationError'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
components:
  schemas:
    MonitorPromptResponse:
      type: object
      properties:
        success:
          type: boolean
          const: true
        data:
          type: object
          properties:
            monitor:
              type: object
              properties:
                id:
                  type: string
                name:
                  type: string
                engines:
                  type: array
                  items:
                    $ref: '#/components/schemas/MonitorEngine'
                aliases:
                  type: array
                  items:
                    type: string
            prompt:
              type: string
            series:
              type: array
              items:
                type: object
                properties:
                  day:
                    type: string
                    format: date-time
                  engine:
                    $ref: '#/components/schemas/MonitorEngine'
                  runs:
                    type: integer
                  mentioned:
                    type: integer
                  cited:
                    type: integer
            topDomains:
              type: array
              maxItems: 12
              items:
                type: object
                properties:
                  domain:
                    type: string
                  citations:
                    type: integer
                  prompts:
                    type: integer
                  own:
                    type: boolean
            topPages:
              type: array
              maxItems: 20
              items:
                type: object
                properties:
                  url:
                    type: string
                  domain:
                    type: string
                  label:
                    type:
                      - string
                      - 'null'
                  citations:
                    type: integer
                  prompts:
                    type: integer
                  own:
                    type: boolean
            results:
              type: array
              maxItems: 100
              items:
                type: object
                properties:
                  taskId:
                    type: string
                  engine:
                    $ref: '#/components/schemas/MonitorEngine'
                  prompt:
                    type: string
                  mentioned:
                    type: boolean
                  cited:
                    type: boolean
                  position:
                    type:
                      - integer
                      - 'null'
                  ranAt:
                    type: string
                    format: date-time
                  competitorHits:
                    type: array
                    items:
                      type: string
            windowDays:
              type: integer
              enum:
                - 7
                - 30
                - 90
    MonitorEngine:
      type: string
      description: >-
        An engine a monitor can schedule: the prompt surfaces sold to customers
        plus the deprecated NAVER alias. GOOGLE_AIO and GOOGLE_AIMODE are
        accepted as input aliases and echoed as GOOGLE and AIMODE.
        CITATION_ANALYSIS is an analysis task, not a prompt surface, and cannot
        be scheduled on a monitor.
      enum:
        - CHATGPT
        - GEMINI
        - PERPLEXITY
        - GOOGLE
        - AIMODE
        - NAVER_AI_BRIEF
        - NAVER_AI_TAB
        - NAVER
    ErrorResponse:
      type: object
      required:
        - success
        - error
      properties:
        success:
          type: boolean
          const: false
        error:
          $ref: '#/components/schemas/ErrorDetail'
    ErrorDetail:
      type: object
      required:
        - code
        - message
      properties:
        code:
          type: string
          description: Stable, safe to branch on. See the Errors guide for the full list.
        message:
          type: string
          description: For humans. May change.
        details:
          description: >-
            Context for the error. An array of `{field, message}` on most
            `VALIDATION_ERROR`s; an object elsewhere (for example `{id}` on
            `RESOURCE_NOT_FOUND`, `retryAfterSec` on 429 and 503 codes). Omitted
            when there is nothing to add.
          oneOf:
            - type: array
              items:
                type: object
                properties:
                  field:
                    type: string
                  message:
                    type: string
            - type: object
              additionalProperties: true
        timestamp:
          type: string
          format: date-time
  responses:
    ValidationError:
      description: >-
        The request is malformed — bad JSON, unrecognised `taskType`, or neither
        `payload.prompt` nor `payload.query` present. `details` names the
        offending field.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          examples:
            missingPrompt:
              summary: Neither prompt nor query supplied
              value:
                success: false
                error:
                  code: VALIDATION_ERROR
                  message: Request validation failed
                  details:
                    - field: payload.prompt
                      message: payload.prompt or payload.query is required
                  timestamp: '2026-07-09T04:12:00.000Z'
            badTaskType:
              summary: Unrecognised taskType
              value:
                success: false
                error:
                  code: VALIDATION_ERROR
                  message: Request validation failed
                  details:
                    - field: taskType
                      message: '''NOPE'' is not recognized'
                  timestamp: '2026-07-09T04:12:00.000Z'
    Unauthorized:
      description: Missing or invalid bearer token.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            error:
              code: MISSING_API_KEY
              message: Missing or invalid API key
              timestamp: '2026-07-09T04:12:00.000Z'
    NotFound:
      description: >-
        No monitor with that id for this key, or no scored row with that task
        id. A monitor owned by another account is reported the same way rather
        than as a 403.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            success: false
            error:
              code: NOT_FOUND
              message: No monitor with that id
              timestamp: '2026-09-22T04:12:00.000Z'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: 'Your API key, sent as `Authorization: Bearer <key>`.'

````

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