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

# Trigger Monitor Run API Reference

> Runs a monitor once, outside its schedule. A manual run always fetches fresh pages and doesn't change the schedule. Get the result from [Get Monitor Run](/api-reference/get-monitor-run) with the returned `run_id`.

The run isn't triggered when:

- The previous run is still `queued` or `processing`: returns `409101`.
- The monitor is paused: returns `409103`. Resume it first by sending `status: active` with [Update Monitor](/api-reference/patch-monitor), then trigger.
- Less than 3 seconds have passed since the last manual trigger: returns `429`.



## OpenAPI

````yaml /api-reference/openapi.json post /monitors/{id}/trigger
openapi: 3.1.0
info:
  title: Octen API
  description: >-
    Octen API provides Broad Search, Web Search, Image Search, Video Search,
    Extract, Embeddings, VL Embeddings, Answer, and Deep Research services. The
    Web Search API searches ranked web results with optional filters,
    highlights, and full content. The Image Search API searches for images from
    a text query or an image. The Video Search API searches for videos from a
    text query. The Broad Search API decomposes a query into multiple
    sub-queries, searches them in parallel, and returns results grouped by
    sub-query. The Extract API extracts clean content from URLs, with optional
    query-focused highlights, page classification, and multimedia resources. The
    Embeddings API converts text into vector representations. The VL Embeddings
    API converts multimodal inputs into vector representations. The Answer API
    decomposes queries into multiple sub-queries for comprehensive search and
    synthesis. The Deep Research API runs a multi-round adaptive research
    pipeline that produces a structured research plan, executes iterative
    searches, and streams a final long-form report. The Pulse Search API
    generates the most likely URLs for a query in about 10ms, with optional
    highlights and full content in standard mode. The Monitor API watches a
    topic or a set of pages on a schedule, records changes that meet your
    condition as events, and pushes them by webhook or email, or lets you pull
    them through the API.
  version: 1.0.0
servers:
  - url: https://api.octen.ai
security:
  - bearerAuth: []
  - apiKeyAuth: []
paths:
  /monitors/{id}/trigger:
    post:
      summary: Trigger a monitor run
      description: >-
        Runs a monitor once, outside its schedule. A manual run always fetches
        fresh pages and doesn't change the schedule. Get the result from [Get
        Monitor Run](/api-reference/get-monitor-run) with the returned `run_id`.


        The run isn't triggered when:


        - The previous run is still `queued` or `processing`: returns `409101`.

        - The monitor is paused: returns `409103`. Resume it first by sending
        `status: active` with [Update Monitor](/api-reference/patch-monitor),
        then trigger.

        - Less than 3 seconds have passed since the last manual trigger: returns
        `429`.
      operationId: post-monitor-trigger
      parameters:
        - $ref: '#/components/parameters/MonitorId'
      responses:
        '200':
          description: Successful trigger response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MonitorTriggerResponse'
              example:
                code: 0
                msg: success
                request_id: req_abc123def456
                data:
                  run_id: run_791
                  status: queued
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/InsufficientBalance'
        '404':
          $ref: '#/components/responses/MonitorNotFound'
        '409':
          description: >-
            Conflict — Returned when the previous run is still `queued` or
            `processing` (code 409101), or the monitor is paused (code 409103).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                code: 409101
                msg: Previous run still in progress
                request_id: req_abc123def456
        '429':
          $ref: '#/components/responses/RateLimited'
        '500':
          $ref: '#/components/responses/InternalError'
components:
  parameters:
    MonitorId:
      name: id
      in: path
      required: true
      schema:
        type: string
      example: mon_123
      description: The monitor id returned by Create Monitor.
  schemas:
    MonitorTriggerResponse:
      type: object
      required:
        - request_id
      properties:
        code:
          type: integer
          description: Business status code. 0 indicates success.
        msg:
          type: string
          description: A message describing the result.
        request_id:
          type: string
          description: The unique identifier for this request.
        data:
          type: object
          properties:
            run_id:
              type: string
              description: The id of this manual run.
            status:
              type: string
              description: '`queued` when triggered.'
    ErrorResponse:
      type: object
      properties:
        code:
          type: integer
          description: Business status code. Non-zero values indicate an error.
        msg:
          type: string
          description: A message describing the error.
        request_id:
          type: string
          description: Unique identifier for the request.
      required:
        - code
        - msg
        - request_id
  responses:
    Unauthorized:
      description: Invalid API Key — Returned when the API key is missing or invalid.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            code: 401
            msg: Invalid API Key
            request_id: req_abc123def456
    InsufficientBalance:
      description: >-
        Insufficient balance in account — Returned when the account balance is
        insufficient to complete the request.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            code: 403
            msg: Insufficient balance in account
            request_id: req_abc123def456
    MonitorNotFound:
      description: >-
        Monitor not found — Returned when the monitor id does not exist or was
        deleted.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            code: 404
            msg: Monitor not found
            request_id: req_abc123def456
    RateLimited:
      description: >-
        Exceeding the rate limit — Returned when the request exceeds the
        configured rate limit.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            code: 429
            msg: Exceeding the rate limit
            request_id: req_abc123def456
    InternalError:
      description: Internal error — Returned when an unexpected server-side error occurs.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            code: 500
            msg: Internal error
            request_id: req_abc123def456
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        Bearer token used for request authentication. Alternatively, you can
        send the API key in the `x-api-key` header. Note: A payment method is
        required to use the API.
    apiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        API key used for request authentication. Alternatively, you can send the
        key as a Bearer token in the `Authorization` header. Note: A payment
        method is required to use the API.

````

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