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

# Start a bulk job on findings

> Start one job that runs triage on, reviews, archives or restores many findings of your team. The selection is either up to 1,000 explicit finding ids, or a queue filter (the filters of GET /api/v1/triage/findings) with the queue version the caller saw and the ids the caller unticked ("select all N matching"). A filter selection is bound to what the caller could have seen: it is resolved on the server while the job runs, in keyset chunks of 1,000 with no limit on the number of matches, but a match first seen after the job was submitted is not part of it, and a review job leaves alone a finding whose review changed after submission (counted in `skipped`). The job is processed in the background in transactions of 100 findings, each finding through the same rules as its single-finding route (visibility, role, review version, run admission and the team's run cap: a run past the cap waits queued), with the progress committed in the same transaction. Bulk jobs share the triage workers with synchronizations, so a team runs one bulk job at a time and the deployment a few (configured); a job over that waits `queued`. A job still live 24 hours after it was submitted fails with `bulk_job_expired`. A finding that cannot be changed is counted in `failed` (a hidden or unknown id, a review refused by the rules) or `skipped` (the change would change nothing, the finding changed after submission, or, for a run job, a run of the finding is in flight or this job already started one); per-finding codes are not kept. A run job starts at most one run per finding, also when its work is retried after an interruption. Poll GET /api/v1/triage/bulk/{id} for progress. Viewers cannot start jobs; archive and unarchive need a team admin, like the single route. Finished jobs are kept 30 days.




## OpenAPI

````yaml /openapi/neo.public.openapi.json post /api/v1/triage/bulk
openapi: 3.1.0
info:
  contact:
    name: ProjectDiscovery
    url: https://neo.projectdiscovery.io
  description: Neo API Server - Security agent orchestration platform
  license:
    name: Apache 2.0
    url: https://www.apache.org/licenses/LICENSE-2.0
  title: Neo API
  version: 1.0.0
servers:
  - description: Production
    url: https://neo.api.projectdiscovery.io
  - description: Development
    url: https://neo.api.dev.projectdiscovery.io
  - description: Local development
    url: http://localhost:8080
security: []
tags:
  - description: Task execution and management
    name: Tasks
  - description: Agent listing and management
    name: Agents
  - description: Public agent directory
    name: Agent Directory
  - description: User file storage management
    name: Files
  - description: User working memory management
    name: Memory
  - description: Scheduled and recurring task management
    name: Schedules
  - description: Knowledge base and semantic search
    name: Knowledge
  - description: Encrypted user credentials and API keys
    name: Secrets
  - description: Neo API key management for programmatic access
    name: API Keys
  - description: User profile and account information
    name: User
  - description: Task and LLM usage tracking
    name: Usage
  - description: Bring Your Own Key provider management
    name: BYOK
  - description: Connect personal AI provider accounts and select them as a model source
    name: AI Connections
  - description: Model discovery and capabilities
    name: Models
  - description: Third-party integrations
    name: Integrations
  - description: Skill knowledge documents for agent prompts
    name: Skills
  - description: User-authored tools and toolkit management
    name: Dynamic Tools
  - description: Team management and member invitations
    name: Teams
  - description: Prompt library management and discovery
    name: Prompts
  - description: Slack bot integration for workspace installation and OAuth
    name: Slack
  - description: GitHub integration for PR reviews and repository management
    name: GitHub
  - description: Vulnerability issue tracking and management
    name: Issues
  - description: Subscription billing and plans
    name: Billing
  - description: Project management and member assignments
    name: Projects
  - description: SSH key pair generation and management for remote server access
    name: SSH Keys
  - description: Captured HTTP traffic query and replay
    name: Network Events
  - description: User and team API activity metadata
    name: Audit Logs
  - description: Vulnerability triage for HackerOne, GitHub, and Security Inbox
    name: Triage
paths:
  /api/v1/triage/bulk:
    post:
      tags:
        - Triage
      summary: Start a bulk job on findings
      description: >
        Start one job that runs triage on, reviews, archives or restores many
        findings of your team. The selection is either up to 1,000 explicit
        finding ids, or a queue filter (the filters of GET
        /api/v1/triage/findings) with the queue version the caller saw and the
        ids the caller unticked ("select all N matching"). A filter selection is
        bound to what the caller could have seen: it is resolved on the server
        while the job runs, in keyset chunks of 1,000 with no limit on the
        number of matches, but a match first seen after the job was submitted is
        not part of it, and a review job leaves alone a finding whose review
        changed after submission (counted in `skipped`). The job is processed in
        the background in transactions of 100 findings, each finding through the
        same rules as its single-finding route (visibility, role, review
        version, run admission and the team's run cap: a run past the cap waits
        queued), with the progress committed in the same transaction. Bulk jobs
        share the triage workers with synchronizations, so a team runs one bulk
        job at a time and the deployment a few (configured); a job over that
        waits `queued`. A job still live 24 hours after it was submitted fails
        with `bulk_job_expired`. A finding that cannot be changed is counted in
        `failed` (a hidden or unknown id, a review refused by the rules) or
        `skipped` (the change would change nothing, the finding changed after
        submission, or, for a run job, a run of the finding is in flight or this
        job already started one); per-finding codes are not kept. A run job
        starts at most one run per finding, also when its work is retried after
        an interruption. Poll GET /api/v1/triage/bulk/{id} for progress. Viewers
        cannot start jobs; archive and unarchive need a team admin, like the
        single route. Finished jobs are kept 30 days.
      operationId: post-v1-triage-bulk
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/TriageBulkRequest'
        required: true
      responses:
        '202':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TriageBulkJobResponse'
          description: The job, queued
        '400':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: >
            A selection with both or neither of ids and filter, an unknown
            filter value, a review action that is missing or not allowed in bulk
            (invalid_request, snooze_invalid), an invalid model (invalid_model),
            or you are not a member of a team
        '401':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: Authentication required
        '402':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: Insufficient credits or usage for a run job (the task error codes)
        '403':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: >-
            Viewers cannot start jobs, members cannot archive (forbidden);
            reviews are turned off (reviews_disabled); or triage is not enabled
            for the account (triage_disabled)
        '409':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: Triage runs are paused for the team (triage_runs_paused)
        '500':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: Unexpected server error
        '503':
          $ref: '#/components/responses/TriageSourcesUnavailable'
      security:
        - BearerAuth: []
        - ApiKeyAuth: []
components:
  schemas:
    TriageBulkRequest:
      additionalProperties: false
      description: A bulk job on findings of your team.
      properties:
        action:
          $ref: '#/components/schemas/TriageBulkAction'
        kind:
          description: >
            `run` starts a triage run on each finding, `review` applies one
            review action, `archive` and `unarchive` archive or restore.
          enum:
            - run
            - review
            - archive
            - unarchive
          type: string
          x-enum-varnames:
            - TriageBulkKindRun
            - TriageBulkKindReview
            - TriageBulkKindArchive
            - TriageBulkKindUnarchive
        selection:
          $ref: '#/components/schemas/TriageBulkSelection'
      required:
        - kind
        - selection
      type: object
    TriageBulkJobResponse:
      properties:
        job:
          $ref: '#/components/schemas/TriageBulkJob'
      required:
        - job
      type: object
    ErrorResponse:
      properties:
        code:
          description: >
            Stable machine-readable error code — branch on this rather than

            matching the human `error`/`message` strings. `access_restricted`

            (HTTP 403) denies hosted Neo access under the access policy. On team

            invitations, param=email identifies a restricted recipient rather

            than the caller; show the error without redirecting the caller.
            Domain codes include

            `user_spending_cap_reached`, `project_spending_cap_reached`, and

            `insufficient_neo_credits`; Free/usage codes include

            `free_grant_challenge_required`, `free_usage_exhausted`,

            `free_task_budget_exhausted`, `model_not_available_on_free`,

            `sandbox_not_available_on_free` (cloud sandbox surfaces are not

            available on the Free plan; task files remain available from the

            task), `free_cannot_continue_managed_task` (a task that ran on the

            standard cloud sandbox cannot be continued on the Free plan; start

            a new task), `free_origin_not_supported` (integration-originated

            tasks are not available on the Free plan),

            `weekly_usage_limit_reached`, `billing_period_usage_limit_reached`,

            `topup_required`, `subscription_required`, and

            `isolated_workspace_purged`. Custom agent authoring codes:

            `agent_not_found`, `agent_not_editable`, `agent_version_conflict`,

            `agent_edit_access_requires_team`, and `agent_invalid_editors`.
            Otherwise it mirrors the error kind

            (e.g. `forbidden`, `invalid_request`, `not_exists`,
            `already_exists`).
          example: user_spending_cap_reached
          type: string
        error:
          example: Bad request
          type: string
        error_id:
          description: Correlation id for a specific error instance, when present.
          type: string
        kind:
          description: Coarse error category (e.g. "forbidden request", "invalid request").
          example: forbidden request
          type: string
        message:
          description: |
            Human-readable detail (the kind prefixed to the error). For display,
            not for branching.
          type: string
        param:
          description: >-
            Field rejected by the policy; email for a restricted invite
            recipient.
          type: string
        turnstile_site_key:
          description: |
            Public Cloudflare Turnstile site key returned only with
            `free_grant_challenge_required`, so the client can complete the
            invisible verification before retrying the request.
          type: string
      required:
        - error
      type: object
    TriageBulkAction:
      additionalProperties: false
      description: >
        What the job does to each finding. A review job needs review_action (and
        the fields that action needs, as in POST
        /api/v1/triage/findings/{id}/review); a run job may name a model.
        Archive and unarchive take nothing.
      properties:
        model:
          description: The model of a run job; omitted, the default model of a run.
          maxLength: 200
          type: string
        note:
          description: Note of the change, kept on each event.
          maxLength: 2000
          type: string
        reason:
          description: Required for decline.
          enum:
            - false_positive
            - accepted_risk
            - wont_fix
          type: string
          x-enum-varnames:
            - TriageBulkReasonFalsePositive
            - TriageBulkReasonAcceptedRisk
            - TriageBulkReasonWontFix
        review_action:
          description: >
            The review action of a review job. mark_duplicate and the fix
            actions need a per-finding target and are not offered in bulk.
          enum:
            - accept
            - decline
            - snooze
            - return_to_queue
            - set_severity
            - clear_severity
          type: string
          x-enum-varnames:
            - TriageBulkReviewActionAccept
            - TriageBulkReviewActionDecline
            - TriageBulkReviewActionSnooze
            - TriageBulkReviewActionReturnToQueue
            - TriageBulkReviewActionSetSeverity
            - TriageBulkReviewActionClearSeverity
        severity:
          description: Required for set_severity.
          enum:
            - none
            - low
            - medium
            - high
            - critical
          type: string
          x-enum-varnames:
            - TriageBulkSeverityNone
            - TriageBulkSeverityLow
            - TriageBulkSeverityMedium
            - TriageBulkSeverityHigh
            - TriageBulkSeverityCritical
        until:
          description: Required for snooze. In the future and at most one year ahead.
          format: date-time
          type: string
      type: object
    TriageBulkSelection:
      additionalProperties: false
      description: >
        The findings of the job: either `ids`, or `filter` with the `version` of
        the queue the caller saw and the `excluded` ids. Exactly one of ids and
        filter.
      properties:
        excluded:
          description: Finding ids of the filter's matches to leave out.
          items:
            format: uuid
            type: string
          maxItems: 1000
          type: array
        filter:
          $ref: '#/components/schemas/TriageBulkFilter'
        ids:
          items:
            format: uuid
            type: string
          maxItems: 1000
          minItems: 1
          type: array
        version:
          description: >-
            The queue version (ETag version) the filter selection was made at;
            recorded on the job.
          maxLength: 64
          type: string
      type: object
    TriageBulkJob:
      description: >
        A bulk job and its progress. `total` is the size of an id selection; for
        a filter selection it is an estimate until the job completes (bounded at
        10,001 while the matches are read, then the exact number processed).
        touched + failed + skipped is the progress.
      properties:
        can_undo:
          description: >-
            A review, archive or unarchive job that ended (completed, or failed
            after it changed findings) with changes and no undo yet, or whose
            undo failed (undo_failed).
          type: boolean
        completed_at:
          format: date-time
          nullable: true
          type: string
        created_at:
          format: date-time
          type: string
        error_code:
          description: >-
            Why a failed job or a failed undo stopped (for example forbidden,
            requester_gone, triage_runs_paused, internal_error,
            bulk_job_expired).
          nullable: true
          type: string
        failed:
          description: Findings the job could not change.
          type: integer
        id:
          format: uuid
          type: string
        kind:
          enum:
            - run
            - review
            - archive
            - unarchive
          type: string
          x-enum-varnames:
            - TriageBulkJobKindRun
            - TriageBulkJobKindReview
            - TriageBulkJobKindArchive
            - TriageBulkJobKindUnarchive
        selection:
          description: Whether the job was given ids or a filter.
          enum:
            - ids
            - filter
          type: string
          x-enum-varnames:
            - TriageBulkJobSelectionIds
            - TriageBulkJobSelectionFilter
        skipped:
          description: >-
            Findings the change would not have changed, or (filter selection)
            that changed after the job was submitted.
          type: integer
        status:
          description: >
            queued and running while the job or its undo is processed; completed
            or failed when it ended; undo_failed when the job ended
            (`completed_at` and its counters) and its undo stopped before it
            finished (`error_code` says why; the undo can be requested again).
          enum:
            - queued
            - running
            - completed
            - failed
            - undo_failed
          type: string
          x-enum-varnames:
            - TriageBulkJobStatusQueued
            - TriageBulkJobStatusRunning
            - TriageBulkJobStatusCompleted
            - TriageBulkJobStatusFailed
            - TriageBulkJobStatusUndoFailed
        total:
          type: integer
        touched:
          description: Findings the job changed (for a run job, runs started or queued).
          type: integer
        undo:
          $ref: '#/components/schemas/TriageBulkUndo'
        undone_at:
          format: date-time
          nullable: true
          type: string
        updated_at:
          format: date-time
          type: string
        version:
          description: The queue version a filter selection was made at.
          nullable: true
          type: string
      required:
        - id
        - kind
        - status
        - selection
        - total
        - touched
        - failed
        - skipped
        - can_undo
        - created_at
        - updated_at
        - completed_at
        - undone_at
        - error_code
      type: object
    TriageBulkFilter:
      additionalProperties: false
      description: >
        A queue filter, with the meaning of the parameters of the same names of
        GET /api/v1/triage/findings. The matches are read when the job runs,
        less those first seen after the job was submitted.
      properties:
        archived:
          type: boolean
        context:
          items:
            maxLength: 256
            type: string
          maxItems: 50
          type: array
        include_snoozed:
          type: boolean
        q:
          maxLength: 200
          type: string
        severity:
          items:
            enum:
              - critical
              - high
              - medium
              - low
              - none
            type: string
          maxItems: 5
          type: array
        sla:
          enum:
            - overdue
            - due_soon
          type: string
        source_id:
          items:
            format: uuid
            type: string
          maxItems: 50
          type: array
        source_kind:
          items:
            $ref: '#/components/schemas/TriageSourceKind'
          maxItems: 5
          type: array
        stage:
          items:
            enum:
              - untriaged
              - investigating
              - verdict_ready
              - in_fix
              - closed
            type: string
          maxItems: 5
          type: array
        state:
          items:
            maxLength: 128
            type: string
          maxItems: 20
          type: array
        verdict:
          items:
            enum:
              - valid
              - need_more_info
              - duplicate
              - informative
              - not_applicable
              - spam
              - unknown
            type: string
          maxItems: 7
          type: array
        view:
          enum:
            - all
            - needs_decision
            - critical_high
            - in_fix
            - waiting
            - snoozed
          type: string
      type: object
    TriageBulkUndo:
      description: The undo of a job, once requested.
      properties:
        failed:
          description: Changes the undo could not reverse.
          type: integer
        requested_at:
          format: date-time
          type: string
        reverted:
          description: Changes undone.
          type: integer
        skipped:
          description: Changes left alone because the finding changed since.
          type: integer
      required:
        - requested_at
        - reverted
        - skipped
        - failed
      type: object
    TriageSourceKind:
      description: >
        hackerone, github and gmail are built-in connections; custom_api is a
        source you configure.
      enum:
        - hackerone
        - github
        - gmail
        - custom_api
        - scanner
      type: string
      x-enum-varnames:
        - TriageSourceKindHackerone
        - TriageSourceKindGithub
        - TriageSourceKindGmail
        - TriageSourceKindCustomApi
        - TriageSourceKindScanner
  responses:
    TriageSourcesUnavailable:
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
      description: >-
        This deployment has no custom source tables yet: its database migration
        has not run (custom_sources_unavailable). Retry later.
  securitySchemes:
    BearerAuth:
      bearerFormat: JWT
      description: JWT authentication token
      scheme: bearer
      type: http
    ApiKeyAuth:
      description: Neo API key (neo_sk_* prefix)
      in: header
      name: X-Api-Key
      type: apiKey

````

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