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

# Get Full Analysis Report

> Generates a sectioned CSV analysis report for a specific repository and commit, covering up to ten categories: SAST, Secrets, SCA, IaC, Anti-Patterns, Complex Functions, Docstring, Duplicate Code, Dead Code, and SBOM. Each category is emitted as its own labeled section with category-specific columns. By default, issues dismissed via the admin UI's dismiss-alerts workflow and issues flagged as false positives are excluded - use `include_dismissed` / `include_false_positives` to override. Returns a presigned URL for the resulting CSV.



## OpenAPI

````yaml /openapi.json post /api/analysis/results/full_report
openapi: 3.0.3
info:
  title: CodeAnt AI API
  description: >-
    API for code analysis (SAST, SCA, secrets, IaC) and developer productivity
    metrics. Supports GitHub, GitLab, Bitbucket, and Azure DevOps.
  version: 1.0.0
servers:
  - url: https://api.codeant.ai
    description: Production server
security: []
tags:
  - name: Analysis
    description: Code analysis operations
  - name: Agent Analysis
    description: >-
      AI-powered agent analysis operations. Uses LLM-based code exploration
      agents to perform deep security threat hunting, bug finding, and custom
      analysis with reflection-based false positive filtering.
  - name: Developer Metrics - Teams
    description: >-
      Manage developer teams: create, update, delete teams and manage team
      membership. Teams are used to organize developers and scope metrics.
  - name: Developer Metrics
    description: >-
      Developer productivity and activity metrics: active developers, PR
      throughput, individual comparisons, and AI-generated summaries. All
      endpoints support GitHub, GitLab, Bitbucket, and Azure DevOps.
  - name: Audit Logs
    description: >-
      Read-only access to your organization's audit trail for compliance, ETL
      and SIEM ingestion. Events are immutable, retained for 180 days, and cover
      security-relevant actions: user management, access control, credentials,
      scan triggers, configuration changes and data exports. Secrets and tokens
      are redacted and never appear in any response format.
  - name: Container Scanning
    description: >-
      Container image vulnerability scanning across AWS ECR, Azure ACR, and GCP
      GAR registries. List tracked containers with their latest scan, then fetch
      the full vulnerability findings of a scan — the same data shown on the
      Cloud Security → Container Scanning page. Authenticate with a CodeAnt API
      token (requires the `view_cloud_security: read` permission when token
      scoping is configured).
  - name: Security Hotlist
    description: >-
      The organization-wide security Hotlist: every SCA, SAST, secrets, IaC,
      cloud (CSPM) and AI-exploitation finding, deduplicated and priority-scored
      into one ranked list with live ticket, assignee and SLA state. Query it
      with filters, facets and cursor pagination, or export the full filtered
      list as an Excel workbook. Authenticate with a CodeAnt API token (requires
      the `view_code_security: read` permission when token scoping is
      configured).
paths:
  /api/analysis/results/full_report:
    post:
      tags:
        - Analysis
      summary: Get Full Analysis Report
      description: >-
        Generates a sectioned CSV analysis report for a specific repository and
        commit, covering up to ten categories: SAST, Secrets, SCA, IaC,
        Anti-Patterns, Complex Functions, Docstring, Duplicate Code, Dead Code,
        and SBOM. Each category is emitted as its own labeled section with
        category-specific columns. By default, issues dismissed via the admin
        UI's dismiss-alerts workflow and issues flagged as false positives are
        excluded - use `include_dismissed` / `include_false_positives` to
        override. Returns a presigned URL for the resulting CSV.
      operationId: getFullReport
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/FullReportRequest'
            examples:
              github:
                summary: GitHub repository example with default fields
                value:
                  repo: owner/repository
                  commit_id: abc123def456
                  access_token: ghp_xxxxxxxxxxxx
                  service: github
                  branch: main
                  fields:
                    - Static Application Security Testing (SAST)
                    - Secrets
                    - Software Composition Analysis (SCA)
                    - Infrastructure as Code
                    - Anti-Patterns
                    - Complex Functions
                    - Docstring
                    - Duplicate Code
                    - Dead Code
                    - SBOM
              githubIncludeDismissed:
                summary: Include dismissed issues and false positives
                value:
                  repo: owner/repository
                  commit_id: abc123def456
                  access_token: ghp_xxxxxxxxxxxx
                  service: github
                  branch: main
                  include_dismissed: true
                  include_false_positives: true
              azuredevops:
                summary: Azure DevOps repository example
                value:
                  repo: organization/project/repository
                  commit_id: abc123def456
                  access_token: pat_xxxxxxxxxxxx
                  service: azuredevops
                  branch: develop
                  azure_devops_base_url: https://dev.azure.com
              gitlab:
                summary: GitLab repository example
                value:
                  repo: group/repository
                  commit_id: abc123def456
                  access_token: glpat_xxxxxxxxxxxx
                  service: gitlab
                  branch: main
                  gitlab_base_url: https://gitlab.com
              bitbucket:
                summary: Bitbucket repository example
                value:
                  repo: workspace/repository
                  commit_id: abc123def456
                  access_token: bitbucket_token
                  service: bitbucket
                  branch: main
                  bitbucket_base_url: https://api.bitbucket.org/2.0
      responses:
        '200':
          description: Full report generated successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/FullReportResponse'
              example:
                report_url: >-
                  https://storage.example.com/reports/owner-repository-abc123def456.html
                status: success
                commit_id: abc123def456
                branch: main
        '400':
          description: Missing required parameters
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error: >-
                  Missing required parameters: repo, commit_id, access_token,
                  service
        '401':
          description: Invalid access token
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error: Access token invalid
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                error: 'Error generating full report: Failed to fetch analysis results'
components:
  schemas:
    FullReportRequest:
      type: object
      required:
        - repo
        - access_token
        - service
      properties:
        repo:
          type: string
          description: Repository identifier (format varies by service)
          example: owner/repository
        commit_id:
          type: string
          description: >-
            Git commit SHA or identifier. Either commit_id or branch is
            required. If both are provided, commit_id takes precedence.
          example: abc123def456
        access_token:
          type: string
          description: Authentication token for the service
          example: ghp_xxxxxxxxxxxx
        service:
          type: string
          description: Version control service provider
          enum:
            - github
            - azuredevops
            - gitlab
            - bitbucket
          example: github
        branch:
          type: string
          description: >-
            Git branch name. When provided without commit_id, the service
            resolves the latest commit from scan history for this branch. Either
            commit_id or branch is required.
          example: main
        fields:
          type: array
          description: >-
            List of analysis categories to include in the sectioned CSV report.
            Each category becomes its own section with category-specific
            columns.
          items:
            type: string
            enum:
              - Static Application Security Testing (SAST)
              - Secrets
              - Software Composition Analysis (SCA)
              - Infrastructure as Code
              - Anti-Patterns
              - Complex Functions
              - Docstring
              - Duplicate Code
              - Dead Code
              - SBOM
          default:
            - Static Application Security Testing (SAST)
            - Secrets
            - Software Composition Analysis (SCA)
            - Infrastructure as Code
            - Anti-Patterns
            - Complex Functions
            - Docstring
            - Duplicate Code
            - Dead Code
            - SBOM
          example:
            - Static Application Security Testing (SAST)
            - Secrets
            - Software Composition Analysis (SCA)
            - Infrastructure as Code
            - Anti-Patterns
            - Complex Functions
            - Docstring
            - Duplicate Code
            - Dead Code
            - SBOM
        include_dismissed:
          type: boolean
          description: >-
            When true, dismissed issues (those marked as dismissed via the admin
            UI's dismiss-alerts workflow) are included in the report. Defaults
            to false, matching the admin UI behavior where dismissed issues are
            hidden.
          default: false
          example: false
        include_false_positives:
          type: boolean
          description: >-
            When true, issues flagged as false positives are included -
            specifically SAST issues with false_positive=true and Secrets with
            confidence_score=FALSE_POSITIVE. Defaults to false.
          default: false
          example: false
        gitlab_base_url:
          type: string
          description: Base URL for GitLab service (optional)
          default: https://gitlab.com
          example: https://gitlab.com
        github_base_url:
          type: string
          description: Base URL for GitHub service (optional)
          default: https://github.com
          example: https://github.com
        azure_devops_base_url:
          type: string
          description: Base URL for Azure DevOps service (optional)
          default: https://dev.azure.com
          example: https://dev.azure.com
        bitbucket_base_url:
          type: string
          description: Base URL for Bitbucket service (optional)
          default: https://api.bitbucket.org/2.0
          example: https://api.bitbucket.org/2.0
    FullReportResponse:
      type: object
      description: Full analysis report response containing the report URL and status
      properties:
        report_url:
          type: string
          description: URL to access the generated HTML report
          example: >-
            https://storage.example.com/reports/owner-repository-abc123def456.html
        status:
          type: string
          description: Status of the report generation
          enum:
            - success
            - failed
          example: success
        commit_id:
          type: string
          description: Git commit SHA that was analyzed
          example: abc123def456
        branch:
          type: string
          description: Git branch name that was analyzed
          example: main
    ErrorResponse:
      type: object
      properties:
        error:
          type: string
          description: Error message

````

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