> ## Documentation Index > Fetch the complete documentation index at: https://docs.getcliq.io/llms.txt > Use this file to discover all available pages before exploring further. # Acknowledge a review > An agent confirms it received the decision; the review becomes `completed`. Daemon push: requires the daemon's realm token (`cliq_dt_…`) for the realm that owns the review given by `review_id`. ## OpenAPI ````yaml /openapi/hub-by-tag/hub-reviews.yaml post /v1/reviews/ack openapi: 3.0.3 info: title: 'CliqHub API: Reviews' version: 1.0.0 description: >- Human-in-the-loop (HUG) reviews. When a team reaches a review phase, the agent opens a review; CliqHub notifies the reviewers (people and channels named in the team or at run start) and shows the review in their inbox. A reviewer reads it, can chat with the agent, and gives a verdict (`PASS`, `REJECT` or `ROUTE:`); with an `all` policy every group must answer first. The agent then picks up the decision and acknowledges it. A review is `pending`, then `decided`, then `completed` once the agent acknowledged it, or `expired` when nobody answered in time (4 hours by default). servers: - url: https://{host} variables: host: default: cliqhub.io description: CliqHub host security: [] tags: - name: Reviews description: >- Human-in-the-loop (HUG) reviews. When a team reaches a review phase, the agent opens a review; CliqHub notifies the reviewers (people and channels named in the team or at run start) and shows the review in their inbox. A reviewer reads it, can chat with the agent, and gives a verdict (`PASS`, `REJECT` or `ROUTE:`); with an `all` policy every group must answer first. The agent then picks up the decision and acknowledges it. A review is `pending`, then `decided`, then `completed` once the agent acknowledged it, or `expired` when nobody answered in time (4 hours by default). paths: /v1/reviews/ack: post: tags: - Reviews summary: Acknowledge a review description: >- An agent confirms it received the decision; the review becomes `completed`. Daemon push: requires the daemon's realm token (`cliq_dt_…`) for the realm that owns the review given by `review_id`. operationId: POST_v1_reviews_ack requestBody: required: true content: application/json: schema: type: object properties: review_id: type: string minLength: 1 description: The review. run_id: type: string minLength: 1 description: The run; defaults to the review's. required: - review_id examples: default: value: review_id: 4a3b2c1d-0e9f-4a8b-9c7d-6e5f4a3b2c1d responses: '200': description: Success. content: application/json: schema: type: object properties: ok: type: boolean enum: - true description: Always `true` on success. data: type: object properties: status: type: string enum: - completed required: - ok example: ok: true data: status: completed '401': description: >- `unauthorized`: No `Authorization` header, or the token is malformed, expired or revoked. content: application/json: schema: $ref: '#/components/schemas/HubErr' examples: unauthorized: summary: unauthorized value: ok: false error: code: unauthorized message: Authentication required '403': description: >- `forbidden`: You can see the record but your role in its realm is too low or lacks the required permission. `forbidden`: `run_id` is not the review's run. content: application/json: schema: $ref: '#/components/schemas/HubErr' examples: forbidden: summary: forbidden value: ok: false error: code: forbidden message: You do not have access to do this forbidden (endpoint): summary: forbidden (endpoint) value: ok: false error: Run ID mismatch code: forbidden '404': description: >- `not_found`: The review does not exist or is in a realm you cannot see (404 rather than 403, so its existence is not revealed). content: application/json: schema: $ref: '#/components/schemas/HubErr' examples: not_found: summary: not_found value: ok: false error: code: not_found message: Not found '409': description: >- `conflict`: The review is not `decided` (still pending, or already completed). content: application/json: schema: $ref: '#/components/schemas/HubErr' examples: conflict: summary: conflict value: ok: false error: 'Cannot ack review in status: pending' code: conflict '422': description: >- `invalid_params`: The body fails the request schema: a required field is missing or a value has the wrong type or format. The message lists every issue as `field: problem`. content: application/json: schema: $ref: '#/components/schemas/HubErr' examples: invalid_params: summary: invalid_params value: ok: false error: 'review_id: Required' code: invalid_params '500': description: >- `internal_error`: An unexpected server fault. Retry later; if it persists, report it with the time of the request. content: application/json: schema: $ref: '#/components/schemas/HubErr' examples: internal_error: summary: internal_error value: ok: false error: Internal server error code: internal_error security: - BearerAuth: [] components: schemas: HubErr: type: object required: - ok - error description: >- Every failure. Route-policy denials (401/403/404, and 400 when neither realm_id nor org_id was sent) answer `error` as `{ code, message }`; errors raised by the endpoint answer `error` as the message with the code beside it in `code`. Every error has a code. See [Errors](/hub-api/errors). properties: ok: type: boolean description: Always false on error error: description: The message, or `{ code, message }` for an access denial. oneOf: - type: string - type: object required: - code - message properties: code: type: string message: type: string code: type: string description: Stable error code of an endpoint error. details: type: object additionalProperties: true description: Structured detail, when there is some. securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: cliq_tok_* | cliq_dt_* description: >- User PAT (`cliq_tok_…`, including session-scoped) or realm token (`cliq_dt_…`). ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.