---
title: "Add note to application"
method: POST
path: "/ats/applications/{application_id}/notes"
tags: ["Unified ATS API"]
---

# Add note to application

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

Add a note to an application.

Add extra information to an application. This can be any extra text information you want to add to an application.

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

### Example Request Body

```json
{
  "content": "A new message from the candidate is available in YourChat!",
  "content_type": "PLAIN_TEXT",
  "remote_fields": {}
}
```

## Path parameters

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

## Headers

- `X-Integration-Id` string, required

## Request body

- PostAtsApplicationsApplicationIdNotesRequestBody
  - `content` string, required — UTF-8 content of the note.
  - `content_type` 'PLAIN_TEXT', required — Content type of the note. Currently only `PLAIN_TEXT` is supported.
  - `remote_fields` object — Tool specific remote fields for the note.
    - `teamtailor` object — Teamtailor specific remote fields for the note.
      - `user_id` string — ID of the user that created the note. Defaults to the first admin user found.
    - `greenhouse` object — Fields specific to Greenhouse.
      - `visibility` 'admin_only' | 'private' | 'public' — Visibility of the created note.
      - `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 — Greenhouse V3 specific remote fields for the note.
      - `visibility` 'admin_only' | 'private' | 'public' — Visibility of the created note.
    - `recruitee` object — Recruitee specific remote fields for the note.
      - `visibility` unknown
      - `is_json` boolean — Whether the note is in a stringified JSON format. If true, content should contain a valid JSON as per the [Recruitee API documentation](https://docs.recruitee.com/reference/candidatesidnotes) (body_json field). If false we add the note as a plain text.
    - `bullhorn` object — Bullhorn specific remote fields for the note.
      - `action` string — The action (or type) associated with a Note. You can find all available note actions in a Bullhorn instance under System Settings > commentActionList. The default action is `Note`.
    - `lever` object — Lever specific remote fields for the note.
      - `perform_as` string — ID of the Lever user that will show up as having created the note. If not provided, defaults to the user associated with the OAuth token.
    - `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/notes Positive response

- PostAtsApplicationsApplicationIdNotesPositiveResponse
  - `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)