> ## 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.

# List HackerOne reports

> List HackerOne reports available for triage through your team's connected HackerOne account.
Use `scope` to choose which reports to list:
- `program` (default): reports in a program inbox. Pass one or more program handles with `program`, or rely on the connection's default program when set.
- `hacker`: reports you submitted as a researcher. No program handle is required.




## OpenAPI

````yaml https://neo.api.projectdiscovery.io/api/openapi.json get /api/v1/hackerone/reports
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: Model discovery and capabilities
    name: Models
  - description: Third-party integrations
    name: Integrations
  - description: Skill knowledge documents for agent prompts
    name: Skills
  - 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: Codebase structural analysis and mapping
    name: Codemaps
  - description: AI-generated codebase documentation and security analysis
    name: CodeWiki
  - description: Captured HTTP traffic query and replay
    name: Network Events
  - description: Vulnerability triage for HackerOne, GitHub, and Security Inbox
    name: Triage
  - description: >-
      Application-internal endpoints used by the Neo UI. Not part of the public
      customer API surface.
    name: Internal
paths:
  /api/v1/hackerone/reports:
    get:
      tags:
        - Internal
      summary: List HackerOne reports
      description: >
        List HackerOne reports available for triage through your team's
        connected HackerOne account.

        Use `scope` to choose which reports to list:

        - `program` (default): reports in a program inbox. Pass one or more
        program handles with `program`, or rely on the connection's default
        program when set.

        - `hacker`: reports you submitted as a researcher. No program handle is
        required.
      operationId: get-v1-hackerone-reports
      parameters:
        - description: 'Listing scope: "program" (default) or "hacker".'
          in: query
          name: scope
          required: false
          schema:
            enum:
              - program
              - hacker
            type: string
        - description: |
            Program handle(s) to list when scope is program. May be repeated.
          explode: true
          in: query
          name: program
          required: false
          schema:
            items:
              type: string
            type: array
          style: form
        - description: Report state(s) to include. May be repeated.
          explode: true
          in: query
          name: state
          required: false
          schema:
            items:
              type: string
            type: array
          style: form
        - description: >
            Severity rating(s) to include: none, low, medium, high, critical.
            May be repeated. Reports without an assigned severity match "none".
          explode: true
          in: query
          name: severity
          required: false
          schema:
            items:
              enum:
                - none
                - low
                - medium
                - high
                - critical
              type: string
            type: array
          style: form
        - description: Search by title/keyword.
          in: query
          name: keyword
          required: false
          schema:
            type: string
        - description: Sort value (program scope), e.g. "-reports.created_at".
          in: query
          name: sort
          required: false
          schema:
            type: string
        - description: Items per page (1-100, default 25).
          in: query
          name: page_size
          required: false
          schema:
            type: integer
        - description: 1-indexed page number.
          in: query
          name: page
          required: false
          schema:
            type: integer
        - description: >
            Cursor for the next densified neo_triage page (from
            next_page_token). Ignored when neo_triage is all.
          in: query
          name: page_token
          required: false
          schema:
            type: string
        - description: >
            Filter by Neo triage linkage. `yes` = has a Neo triage run, `no` =
            not yet triaged in Neo, `all` (default) = no filter. When set to
            yes/no, the API scans ahead across HackerOne pages to fill page_size
            matches; next_page_token may be an opaque resume cursor.
          in: query
          name: neo_triage
          required: false
          schema:
            enum:
              - all
              - true
              - false
            type: string
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HackerOneReportsResponse'
          description: HackerOne report list
        '400':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: HackerOne is not connected or a program handle is required
        '401':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: Authentication required
        '500':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: Internal server error
        '502':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: Could not reach HackerOne
      security:
        - BearerAuth: []
        - ApiKeyAuth: []
components:
  schemas:
    HackerOneReportsResponse:
      properties:
        next_page_token:
          description: >
            Cursor for the next densified neo_triage page (pass as page_token).
            Omitted when neo_triage is all or there is no further page.
          type: string
        reports:
          items:
            $ref: '#/components/schemas/HackerOneReport'
          type: array
      required:
        - reports
      type: object
    ErrorResponse:
      properties:
        code:
          description: >
            Stable machine-readable error code — branch on this rather than

            matching the human `error`/`message` strings. Domain codes include

            `user_spending_cap_reached`, `project_spending_cap_reached`, and

            `insufficient_neo_credits`; 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
      required:
        - error
      type: object
    HackerOneReport:
      properties:
        created_at:
          description: When the report was created (ISO 8601).
          type: string
        description:
          description: Vulnerability details supplied with the report, when available.
          type: string
        id:
          description: HackerOne report ID.
          example: '1617253'
          type: string
        reporter:
          description: Reporter username, when available.
          type: string
        severity:
          description: Reporter-claimed severity rating, when available.
          example: high
          type: string
        state:
          description: HackerOne report state (e.g. new, triaged, resolved, duplicate).
          example: new
          type: string
        title:
          description: Report title.
          type: string
        triage_task:
          allOf:
            - $ref: '#/components/schemas/TriageTaskSummary'
          description: >
            Linked Neo triage run for this report, when one exists for your
            team. Null when triage has not been started.
          nullable: true
        url:
          description: Link to the report on HackerOne.
          example: https://hackerone.com/reports/1617253
          type: string
      required:
        - id
        - title
        - state
        - url
      type: object
    TriageTaskSummary:
      properties:
        completed_at:
          description: When the triage decision was recorded.
          format: date-time
          nullable: true
          type: string
        created_at:
          description: When this triage run was started or last re-triaged.
          format: date-time
          type: string
        internal_summary:
          description: >
            Team-facing triage write-up, separate from the reporter-ready reply.
            Suitable for an internal HackerOne team comment.
          nullable: true
          type: string
        suggested_response:
          description: |
            Reporter-ready reply text from Neo triage. Paste into HackerOne or
            GitHub when responding to the researcher.
          nullable: true
          type: string
        task_id:
          description: Neo task id for this triage run.
          format: uuid
          type: string
        task_status:
          description: |
            Current Neo task status for this triage run.
          enum:
            - pending
            - active
            - completed
            - error
            - aborted
            - suspended
          nullable: true
          type: string
        triage_severity:
          description: |
            Neo suggested severity. Only set when triage_status is valid;
            otherwise null.
          enum:
            - none
            - low
            - medium
            - high
            - critical
            - unknown
          nullable: true
          type: string
        triage_status:
          description: |
            Neo disposition after the triage task completed. Null while the task
            is still running or has not submitted a decision.
          enum:
            - valid
            - need_more_info
            - duplicate
            - informative
            - not_applicable
            - spam
            - unknown
          nullable: true
          type: string
        triaged_by_email:
          description: |
            Email of the team member who started or last re-triaged this run.
          nullable: true
          type: string
      required:
        - task_id
        - created_at
      type: object
  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

````