Skip to main content
GET
/
reviews
/
{review_id}
/
report
Get Review Report
curl --request GET \
  --url https://api.flightlinehq.com/v1/reviews/{review_id}/report
{
  "generated_at": "2026-05-30T17:42:00Z",
  "issues": [
    {
      "category": "compliance",
      "code": "APR-003",
      "severity": "high",
      "summary": "The disclosed APR is outside the allowed tolerance.",
      "title": "APR tolerance exceeded"
    },
    {
      "category": "documentation",
      "code": "DOC-011",
      "severity": "medium",
      "summary": "A required income document was not found in the package.",
      "title": "Missing income documentation"
    }
  ],
  "outcome": "issues_found",
  "review_id": "9b2c1f3a-4d5e-6789-abcd-ef0123456789",
  "sandbox": false,
  "status": "completed",
  "summary": {
    "critical": 0,
    "high": 1,
    "info": 0,
    "low": 0,
    "medium": 1,
    "total": 2
  }
}

Headers

​
authorization
string | null
​
X-Api-Key
string | null

Path Parameters

​
review_id
string<uuid>
required

Response

Successful Response

The customer-facing report for a completed review.

Only available once the review is completed (i.e. the internal publication gate has released the case). Before that, the report endpoint returns 404 so verdict-adjacent signal never leaks early.

​
generated_at
string<date-time>
required
​
review_id
string<uuid>
required
​
status
enum<string>
required

Customer-facing review lifecycle.

A deliberately coarse projection of the internal CaseStatus. Internal states that are not meaningful to a customer (e.g. the admin-release gate pending_review, the publication-blocker state) collapse to processing so we never surface internal workflow detail or verdict-adjacent signal before the publication gate passes.

Available options:
queued,
awaiting_documents,
processing,
completed,
failed
​
summary
IssueCounts · object
required

Roll-up of issue counts by severity.

Example:
{
  "critical": 0,
  "high": 1,
  "info": 0,
  "low": 0,
  "medium": 1,
  "total": 2
}
​
issues
ReviewIssue · object[]
​
outcome
string | null

Overall outcome, e.g. 'clear' or 'issues_found'.

Example:

"issues_found"

​
sandbox
boolean
default:false

True for sandbox (test-mode) reviews: the issues below are canned sample data.