KOkobaltlabs
internal

Create Admin Review Report

Trigger a one-off reporting agent run against any existing review (including completed ones) using a template uploaded on the spot.

Unlike the customer-facing /reports/review, this never touches the target company's Files table: the template and the generated DOCX/PDF live only in this agent run's own S3 directory ({company_id}/{agent_run_id}/...).

config_variant lets an admin try a ReviewReportConfig experiment (see backend/analyses/reporting/review.py) against a real review without risking a customer-facing run — every other trigger path is hardcoded to STABLE (ReviewReportAgent.execute).

post/internal/reports/review

Request

  • Base URL
    https://api.kobaltlabs.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.kobaltlabs.com/internal/reports/review
  • Auth
    none declared

Request body multipart/form-data

company_idstring uuid required
review_idstring uuid required
project_idstring uuid nullable
config_variant'stable' | 'sonnet' | 'no_thinking'

Which ReviewReportConfig an admin-triggered review_report run used.

STABLE is the only variant reachable from every trigger path (customer-facing /reports/review, the review_reporting_stage_wf task, and admin runs that don't opt into an experiment) — see ReviewReportAgent.execute. The other members are experiment levers, selectable only from the admin report-runner, so a regression in one never reaches a customer's review. See ReviewReportConfig.for_variant (backend/analyses/reporting/review.py) for what each one actually changes.

templatestring binary required

Response

Successful Response

agent_run_idstring uuid required

Changes

No recorded changes to this operation across all 8 revisions of this API.