---
title: "Reject application"
method: POST
path: "/ats/applications/{application_id}/reject"
tags: ["Unified ATS API"]
---

# Reject application

`POST /ats/applications/{application_id}/reject`

Rejects an application with a provided reason.

Rejects an application with a provided reason. Optionally, you can provide a free text note. You can get the list of rejection reasons with our [Get rejection reasons endpoint](/ats/v1/get-rejection-reasons).

<Note>
  This endpoint requires the permission **Reject applications** to be enabled in [your scope config](/scopes).
</Note>

### Example Request Body

```json
{
  "rejection_reason_id": "3PJ8PZhZZa1eEdd2DtPNtVup",
  "note": "Candidate was a great culture fit but didn't bring the hard skills we need.",
  "remote_fields": {}
}
```

## Path parameters

- `application_id` string, required — The Kombo ID of the application you want to reject.

## Headers

- `X-Integration-Id` string, required

## Request body

- PostAtsApplicationsApplicationIdRejectRequestBody
  - `rejection_reason_id` string, required — The Kombo ID of the rejection reason.
  - `note` string — A optional free text rejection note. Passed through if possible.
  - `remote_fields` object — Additional fields that we will pass through to specific ATS systems.
    - `greenhouse` object — Fields specific to Greenhouse.
      - `rejection_email` object — Additional data fields that we will pass through to the `rejection_email` field of Greenhouse's [reject application](https://developers.greenhouse.io/harvest.html#post-reject-application) endpoint.
      - `post_headers` object — Headers we will pass with `POST` requests to Greenhouse.
        - `On-Behalf-Of` string, nullable — ID of the the user that will show up as having performed the action in Greenhouse. We already pass a value by default, but you can use this to override it.
    - `greenhousev3` object — Fields specific to Greenhouse V3.
      - `rejection_email` object — Additional data fields passed through to the `rejection_email` field of Greenhouse V3's reject-application endpoint.
    - `teamtailor` object — Fields specific to Teamtailor.
      - `user_id` string — The remote ID of the user that will be displayed in the UI as the one that performed the action. If not provided, the first admin user will be used.
    - `workable` object — Workable specific remote fields for ATS actions.
      - `on_behalf_of_user_remote_id` string — The remote ID of the user that will be displayed in the UI as the one that performed the action.

## Response `200`

POST /ats/applications/:application_id/reject Positive response

- PostAtsApplicationsApplicationIdRejectPositiveResponse
  - `status` 'success', required
  - `data` object, required
  - `warnings` object[], required — These are the interaction warnings that are shown in the dashboard. They are meant to provide debug information to you. We recommend logging them to the console.
    - `message` string, required

## Other responses

- `default` — The standard error response with the error codes for the ATS use case.

---

[API](https://skmtc.net/kombo/apis/kombo-api.md) · [All operations](https://skmtc.net/kombo/apis/kombo-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/kombo/kombo-api/versions/1e45035b96d3/schema)