---
title: "List scorecard question answers"
method: GET
path: "/v3/scorecard_question_answers"
tags: ["Scorecard Question Answers"]
---

# List scorecard question answers

`GET /v3/scorecard_question_answers`

## Request

- Base URL: `https://harvest.greenhouse.io`
- URL: `https://harvest.greenhouse.io/v3/scorecard_question_answers`
- Auth: one of:
  - OAuth 2
    - Authorization code: `https://auth.greenhouse.io/authorize`
    - Client credentials
    - Token URL: `https://auth.greenhouse.io/token` scopes: `harvest:scorecard_question_answers:list`
  - HTTP bearer

A scorecard question answer is one interviewer's response to a single question on a scorecard. Each row pairs a `scorecard` with a `scorecard_question` and carries the response in `answer` (for `text` questions) or `boolean_value` (for `yes_no` questions); responses to `single_select` and `multi_select` questions are stored as `scorecard_question_answer_options` linked to this row. Filter by `scorecard_ids` to pull every answer on a given scorecard, or by `scorecard_question_ids` to compare how interviewers responded to the same question across scorecards.

## Query parameters

- `cursor` string
- `per_page` integer
- `ids` integer[]
- `created_at` object
  - `gte` string, date-time
  - `lte` string, date-time
  - `gt` string, date-time
  - `lt` string, date-time
- `updated_at` object
  - `gte` string, date-time
  - `lte` string, date-time
  - `gt` string, date-time
  - `lt` string, date-time
- `scorecard_ids` integer[]
- `scorecard_question_ids` integer[]
- `fields` string[]

## Response `200`

Successful

- object[]
  - `id` integer
  - `created_at` string, date-time
  - `updated_at` string, date-time
  - `scorecard_id` integer: Id of the scorecard this answer belongs to. Every answer is tied to exactly one scorecard, which in turn belongs to a single interviewer's submission on one application.
  - `scorecard_question_id` integer: Id of the `scorecard_question` this answer responds to. The question's `answer_type` (`text`, `yes_no`, `single_select`, `multi_select`) determines which field on the answer is populated: `text` uses `answer`, `yes_no` uses `boolean_value`, and `single_select`/`multi_select` use the `scorecard_question_answer_options` sub-resource.
  - `answer` string, nullable: Free-text response for `text`-type scorecard questions. Plain text — HTML formatting and `@`-mention markup are stripped. `null` (or empty string) when the question is `yes_no`, `single_select`, or `multi_select`, or when the interviewer declined to answer.
  - `answer_with_tags` string, nullable: HTML-formatted version of `answer`, preserving rich-text formatting (bold, italic, etc.) and `@`-mentions as embedded user tags (e.g. `@[User Name](user:123)`). `null` when there is no formatting or markup to preserve (i.e. when the stored value would be identical to `answer`), and under the same conditions as `answer`.
  - `boolean_value` boolean, nullable: Response for `yes_no`-type scorecard questions: `true` for yes, `false` for no, `null` when the question is not `yes_no` or when the interviewer left it blank. Ignored on writes for any question whose `answer_type` is not `yes_no`.
  - `value` union: Read-only. The answer in the same vocabulary the nested write path accepts (`question_answers[].value` on `POST`/`PATCH /v3/scorecards`), dispatched on the question's `answer_type`: string for `text`, boolean for `yes_no`, the selected option id for `single_select`, an array of selected option ids for `multi_select`. `null` when unanswered.
    - string
    - boolean
    - integer
    - integer[]

---

[API](https://skmtc.dev/greenhouse/apis/harvest-api.md) - [All operations](https://skmtc.dev/greenhouse/apis/harvest-api/llms.txt) - [OpenAPI document](https://skmtc.dev/greenhouse/apis/harvest-api/revisions/822822e3f771?raw)