---
title: "List advisor reviews"
method: GET
path: "/api/v1/alpha/advisor-reviews"
tags: ["alpha"]
---

# List advisor reviews

`GET /api/v1/alpha/advisor-reviews`

## Request

- Base URL: `https://point11.ai`
- URL: `https://point11.ai/api/v1/alpha/advisor-reviews`
- Auth: one of:
  - HTTP bearer
  - OAuth 2 (authorization code, authorization URL `https://auth.point11.ai/oauth2/authorize`, token URL `https://auth.point11.ai/oauth2/token`)

List the organization's Advisor reviews, newest first: each one's run, why it ran (schedule, launch, run_now, or recovery), the failed review it ran again, its state (running, published, failed, or stale: the list changed while it ran, so another review is owed), when it started and settled, its failure code, and the settings and list revisions it read.

## Query parameters

- `limit` integer: Number of items to return (1–1000)
- `cursor` string: Opaque cursor returned as nextCursor by the previous page

## Headers

- `Point11-Organization` string, uuid

## Response `200`

Success.

- AlphaAdvisorReviewsListResponse
  - `data` object[], required
    - `id` string, uuid, required: The review's run; platform.runs.get reads it
    - `origin` 'schedule' | 'launch' | 'run_now' | 'recovery', nullable, required: Why it ran: its schedule, a Bootup's launch, a person's Run Advisor or saved priorities, or its own recovery; null for a review run before origins were kept
    - `retryOf` string, uuid, nullable, required: The failed review it ran again
    - `state` 'running' | 'published' | 'failed' | 'stale', required: running; published (the list's order is its); failed; stale (the list changed while it ran, so it published nothing and another review is owed)
    - `createdAt` string, date-time, required
    - `completedAt` string, date-time, nullable, required: When it settled; null while it runs
    - `failureCode` string, nullable, required
    - `settingsRevision` integer, nullable, required
    - `baseListRevision` integer, nullable, required
  - `nextCursor` string, nullable, required

## Other responses

- `400`: The input, query, or Idempotency-Key is invalid.
- `401`: The bearer is missing, expired, or not accepted.
- `403`: The credential lacks the operation's scope or role, or the operation needs a different door.
- `404`: The resource or organization does not exist for this caller.
- `405`: This path takes another HTTP method, named in `Allow`.
- `409`: The request conflicts with current state or with prior use of its Idempotency-Key.
- `413`: The request, or the answer it asks for, is too large; narrow it.
- `429`: The credential's rate budget is spent; retry after `Retry-After` seconds.
- `500`: An unexpected server failure; retry later. Only `request_id` identifies it.
- `503`: A dependency is temporarily unavailable; retry after `Retry-After` seconds.
- `default`: Another status a product answers for its own refusal (for example `415` for an unsupported attachment); branch on `code`.

---

[API](https://skmtc.dev/point11/apis/point11-api.md) · [All operations](https://skmtc.dev/point11/apis/point11-api/llms.txt) · [OpenAPI document](https://skmtc.dev/point11/apis/point11-api/revisions/36a84c7aca11?raw)