🚧

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 as that member). An account token without member_id gets 403 Account tokens need a member_id for this operation.

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.

Tasks are always returned from the perspective of the member's own employee record: only tasks where the member is the reviewee, the reviewing manager, or an assigned reviewer are included, regardless of admin permissions. If the member has no linked employee record, both arrays are empty. Archived and deleted cycles return 404.

Tasks are split in two groups:

• preparation_tasks: tasks where the member is the reviewing manager and the review forms still need to be prepared (the cycle is scheduled / in_preparation, or the forms are not yet marked ready). Each review links to its form via update_form_url; read it with GET /review-cycles/:reviewCycleId/tasks/:id/forms/:reviewType, customize it with PUT, and finish preparation with PUT /review-cycles/:reviewCycleId/tasks/:id. Only review types the cycle allows the manager to customize are listed.
• active_tasks: every other task in which the member has something to do or see. reviews lists the reviews assigned to the member as reviewer that are still writable or already submitted, with a view action (GET /review-cycles/:reviewCycleId/reviews/:id) and, while editable, a write action (PUT). Task-level actions may include view (employee review), share (share) and sign (sign); the key is omitted when no action is available. Tasks with neither reviews nor actions are left out.

Within each group tasks are ordered by reviewee name, then manager name.

Results

{
  "preparation_tasks": [
    {
      "id": "4d4",
      "status": "not_ready",
      "review_cycle": {
        "id": "4d6",
        "name": "Mid-year Review 2025",
        "state": "in_preparation",
        "customization_start_date": "2025-05-01T00:00:00.000Z",
        "customization_end_date": "2025-05-15T00:00:00.000Z"
      },
      "reviewee": {
        "id": "4d5",
        "name": "Doe, Jane"
      },
      "reviews": [
        {
          "id": "4d5",
          "type": "self",
          "status": "draft",
          "master_template_id": "2000",
          "follower_template_id": null,
          "update_form_url": "/spi/v3/review-cycles/4d6/tasks/4d4/forms/self"
        },
        {
          "id": "4d6",
          "type": "manager",
          "status": "draft",
          "master_template_id": "3001",
          "follower_template_id": null,
          "update_form_url": "/spi/v3/review-cycles/4d6/tasks/4d4/forms/manager"
        }
      ]
    }
  ],
  "active_tasks": [
    {
      "id": "4d3",
      "state": "in_progress",
      "review_cycle": {
        "id": "4d6",
        "name": "Mid-year Review 2025",
        "state": "in_preparation"
      },
      "reviewee": {
        "id": "4d4",
        "name": "Brown, Alex"
      },
      "reviews": [
        {
          "id": "4e5",
          "type": "manager",
          "state": "submitted",
          "submit_deadline": "2025-06-20T00:00:00.000Z",
          "share_deadline": "2025-06-25T00:00:00.000Z",
          "actions": {
            "view": {
              "url": "/spi/v3/review-cycles/4d6/reviews/4e5"
            }
          }
        }
      ],
      "actions": {
        "view": {
          "url": "/spi/v3/review-cycles/4d6/employees/4d4"
        },
        "share": {
          "url": "/spi/v3/review-cycles/4d6/tasks/4d3/share"
        }
      }
    }
  ]
}

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"}.