🚧

This endpoint uses the r_reviews scope, which must be enabled through the Integrations section found within the Settings menu.

Requires a user token, or an account token together with the member_id query parameter (the request is then evaluated with that member's permissions). An account token without member_id gets 403 Account tokens need a member_id for this operation. member_id is ignored for user tokens.

The member must be able to view review cycles: either through the View review cycles permission (global or scoped role), or through View employee directory in an account with performance reviews enabled. The cycle itself must be visible to the member (see GET /review-cycles); otherwise 404.

Each item is a single answer to a single question. Results are scoped to what the member can see:

• Members with the global View review cycles permission see answers from every review in the cycle.
• Members with a scoped View review cycles role see answers of employees within their scope, plus the answers they can access as an employee.
• All other members see only submitted reviews they can access as an employee: their own reviews and those of their reports. Manager, peer and upward reviews about themselves become visible only once the review has been shared.

Reviewers of anonymous reviews are redacted to {"id": null, "name": "Anonymous"}.

Query parameters

Results

{
  "total_count": 2,
  "answers": [
    {
      "id": "5a1",
      "review_id": "4d3",
      "review_type": "self",
      "question_id": "25012946-72fb-5069-8797-6b5ccc2912dd",
      "question_type": "Paragraph",
      "answer": "I delivered three major projects on time and improved our release process.",
      "choices": [],
      "created_at": "2024-11-05T09:30:00.000Z",
      "updated_at": "2024-11-06T14:12:00.000Z",
      "employee": {
        "id": "4d4",
        "name": "Doe, Jane"
      },
      "reviewer": {
        "id": "4d4",
        "name": "Doe, Jane"
      }
    },
    {
      "id": "5a2",
      "review_id": "4d3",
      "review_type": "self",
      "question_id": "2501297b-1920-5e4c-b21b-fc3caf56b335",
      "question_type": "NumericRated",
      "answer": null,
      "choices": [
        "4"
      ],
      "created_at": "2024-11-05T09:30:00.000Z",
      "updated_at": "2024-11-06T14:12:00.000Z",
      "employee": {
        "id": "4d4",
        "name": "Doe, Jane"
      },
      "reviewer": {
        "id": "4d4",
        "name": "Doe, Jane"
      }
    }
  ]
}

Error responses

Error bodies come in three shapes. 400 validation errors are a JSON object keyed by the invalid parameter, e.g. {"limit": {"code": "number.max", "message": "\"limit\" must be less than or equal to 200"}}. 401 and 403 are plain-text bodies, e.g. Required scopes missing: ["r_reviews"], or Forbidden when the member lacks permission. 404 is JSON, e.g. {"message": "Review cycle not found"}.