---
title: "Retrieve rejection reason"
method: GET
path: "/v3/rejection_reasons/{id}"
tags: ["Rejection Reasons"]
---

# Retrieve rejection reason

`GET /v3/rejection_reasons/{id}`

Retrieve a single rejection reason by id. Use this to resolve the human-readable `name` and the categorization `type` (`We rejected them`, `They rejected us`, `None specified`, or `Security concern`) for a `rejection_reason_id` referenced from a `rejection_details` record on a rejected application. The reason must belong to the calling organization, or — for Greenhouse's built-in default reasons — be returned by the matching list endpoint with `include_defaults=true`.

## Path parameters

- `id` integer, required

## Query parameters

- `fields` string

## Response `200`

Successful

- object
  - `id` integer
  - `created_at` string, date-time
  - `updated_at` string, date-time
  - `name` string — Display label shown to recruiters when rejecting a candidate (e.g. `Not a cultural fit`, `Lacking skill(s)/qualification(s)`, `Wasn't interested`, `Didn't like offer`, `Spam`). Unique within the organization. Free-text, since each organization customizes its own list under Configure > Custom Options > Rejection Reasons. Reason categorization (hire/non-hire, we vs. they rejected) is conveyed by the nested `type` rather than by the name.
  - `type` object — The rejection reason type this reason rolls up to — the categorization Greenhouse uses to interpret outcomes in reporting. Reasons grouped under `We rejected them` mean the organization declined the candidate, `They rejected us` mean the candidate withdrew or declined an offer, `Security concern` flags fraud or other trust signals, and `None specified` is the catch-all. The `Security concern` type is only returned when the `enable_reject_as_security_concern` product flag is on for the organization.
    - `id` integer — Id of the rejection reason type. Stable across all rejection reasons in the organization that share the same categorization.
    - `key` string — Stable machine-readable identifier for the reason type. One of `WE_REJECTED_THEM`, `THEY_REJECTED_US`, `NONE_SPECIFIED`, or `SECURITY_CONCERN`. Prefer matching on `key` over `name` since it is not subject to localization.
    - `name` string — Display name of the rejection reason type used in Greenhouse reporting. One of `We rejected them`, `They rejected us`, `None specified`, or `Security concern`.

## Other responses

- `401` — Unauthorized
- `404` — Not Found

---

[API](https://skmtc.dev/greenhouse/apis/auth-api.md) · [All operations](https://skmtc.dev/greenhouse/apis/auth-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/greenhouse/auth-api/revisions/9517a2e54640/schema)
