---
title: "Get applications"
method: GET
path: "/ats/applications"
tags: ["Unified ATS API"]
---

# Get applications

`GET /ats/applications`

Retrieve all applications.

Visit our in-depth guides to learn more about:

- 💡 [Being aware of which applications are tracked](/ats/features/implementation-guide/tracking-created-applications#be-aware-of-which-applications-are-tracked)
- 🚦 [Hiring signals](/ats/features/implementation-guide/tracking-created-applications#hiring-signals)
- 📈 [Application stage changes](/ats/features/implementation-guide/tracking-created-applications#application-stage-changes)
- ❓ [ATS-specific limitations](/ats/features/implementation-guide/tracking-created-applications#ats-specific-limitations)

Top level filters use AND, while individual filters use OR if they accept multiple arguments. That means filters will be resolved like this: `(id IN ids) AND (remote_id IN remote_ids)`

## Query parameters

- `cursor` string — An optional cursor string used for pagination. This can be retrieved from the `next` property of the previous page response.
- `page_size` integer — The number of results to return per page. Maximum is 250.
- `updated_after` string, date-time — Filter the entries based on the modification date in format `YYYY-MM-DDTHH:mm:ss.sssZ`. Returns records where either the record itself **OR** its nested data has been updated since this timestamp, even if the record's own `changed_at` field remains unchanged. If you want to track entry deletion, also set the `include_deleted=true` query parameter, because otherwise, deleted entries will be hidden. For more details, see [Understanding changed_at vs updated_after Behavior](https://docs.kombo.dev/ats/getting-started/fetching-data#understanding-changed_at-vs-updated_after-behavior). For this endpoint, `updated_after` matches when the returned record changed, or when related data changed as described below. | Path | Added/Removed | Linked Record | | --- | --- | --- | | `candidate` | n/a | ✓ Yes | | `candidate` → `tags` | ✗ No | ✗ No | | `current_stage` | ✗ No | ✗ No | | `job` | ✗ No | ✗ No | | `interviews` | ✓ Yes | ✓ Yes | | `offers` | ✓ Yes | ✓ Yes | _**Added/Removed**: Whether adding or removing entries from this list triggers an update (n/a for single records). **Linked Record**: Whether changes to the linked record itself trigger an update._
- `include_deleted` 'true' | 'false' — By default, deleted entries are not returned. Use the `include_deleted` query param to include deleted entries too.
- `ignore_unsupported_filters` 'true' | 'false' — When set to `true`, filters targeting fields not supported by this integration will be ignored instead of filtering out all results.
- `ids` string — Filter by a comma-separated list of IDs such as `222k7eCGyUdgt2JWZDNnkDs3,B5DVmypWENfU6eMe6gYDyJG3`.
- `remote_ids` string — Filter by a comma-separated list of remote IDs.
- `outcome` 'PENDING' | 'HIRED' | 'DECLINED' — **(⚠️ Deprecated - Use the `outcomes` filter instead.)** Filter applications by outcome. This allows you to get applications that are for example `PENDING`, `HIRED`, or `DECLINED`.
- `outcomes` string — Filter by a comma-separated list of `PENDING`, `HIRED`, `DECLINED` * `PENDING`: The application is still being processed. * `HIRED`: The candidate was hired. * `DECLINED`: The candidate was declined. Leave this blank to get results matching all values.
- `job_ids` string — Filter by a comma-separated list of job IDs. We will only return applications that are related to _any_ of the jobs.
- `job_remote_ids` string — Filter by a comma-separated list of job remote IDs. We will only return applications that are related to _any_ of the jobs.
- `current_stage_ids` string — Filter by a comma-separated list of application stage IDs. We will only return applications that are currently in _any_ of the stages.
- `remote_created_after` string, date-time — Filter applications by the day they were created in the remote system. This allows you to get applications that were created on or after a certain day.

## Headers

- `X-Integration-Id` string, required

## Response `200`

GET /ats/applications Positive response

- GetAtsApplicationsPositiveResponse
  - `status` 'success', required
  - `data` object, required
    - `next` string, nullable, required — Cursor string that can be passed to the `cursor` query parameter to get the next page. If this is `null`, then there are no more pages.
    - `results` object[], required
      - `id` string, required — The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing.
      - `remote_id` string, nullable, required — The raw ID of the object in the remote system. We don't recommend using this as a primary key on your side as it might sometimes be compromised of multiple identifiers if a system doesn't provide a clear primary key.
      - `outcome` 'PENDING' | 'HIRED' | 'DECLINED', nullable, required — Parsed status of the application. If Kombo identifies that the application was accepted and the candidate hired, it will be `HIRED`. If the application was rejected or the candidate declined, it will be `DECLINED`. If the application is still in process, it will be `PENDING`. Kombo will always try to deliver this information as reliably as possible.
      - `rejection_reason_name` string, nullable, required — Reason for the rejection of the candidate.
      - `rejected_at` string, date-time, nullable, required — The time that the application was rejected.
      - `current_stage_id` string, nullable, required — ID of the current application stage
      - `job_id` string, nullable, required — The Kombo ID of the job which the candidate applied to. The ID can be used to retrieve the job from the `get jobs` endpoint.
      - `candidate_id` string, nullable, required — The Kombo ID of the candidate who applied to the job. The ID can be used to retrieve the candidate from the `get candidates` endpoint.
      - `screening_question_answers` union[], nullable — A list of answers to screening questions. The screening answer type `FILE` is currently unsupported.
        - union
          - object
            - `answer` object, required
              - …
            - `question` object, required
              - …
          - object
            - `answer` object, required
              - …
            - `question` object, required
              - …
          - object
            - `answer` object, required
              - …
            - `question` object, required
              - …
          - object
            - `answer` object, required
              - …
            - `question` object, required
              - …
          - object
            - `answer` object, required
              - …
            - `question` object, required
              - …
          - object
            - `answer` object, required
              - …
            - `question` object, required
              - …
          - object
            - `answer` object, required
              - …
            - `question` object, required
              - …
      - `custom_fields` object, nullable, required — A key-value store of fields not covered by the schema. [Read more](/custom-fields)
      - `integration_fields` object[], required — An array of selected passthrough integration fields. [Read more](/integration-fields)
        - `id` string, required — The globally unique ID of this object.
        - `key` string, required — The key of the field in the remote system.
        - `type` 'DEFAULT' | 'CUSTOM', required — - `DEFAULT`: static fields in the remote system. - `CUSTOM`: fields that are created/editable by the user.
        - `value` unknown
        - `label` string, nullable, required — The label of the field. (not always available)
      - `remote_url` string, uri, nullable, required — URL to the application in the source ATS system. When embedding this in your system, please consider that not for all ATS a dedicated application URL is available, so you might need to fall back to the candidate URL.
      - `changed_at` string, date-time, required — The timestamp when this specific record was last modified. This field only updates when properties directly on this record change, NOT when related or nested models change. For filtering that considers nested data changes, use the `updated_after` parameter which will return records when either the record itself OR its related models have been updated.
      - `remote_deleted_at` string, date-time, nullable, required — The date and time the object was deleted in the remote system. Objects are automatically marked as deleted when Kombo can't retrieve them from the remote system anymore. Kombo will also anonymize entries 14 days after they disappear.
      - `remote_created_at` string, date-time, nullable, required — The date and time the object was created in the remote system.
      - `remote_updated_at` string, date-time, nullable, required — A timestamp retrieved from the remote system, describing when the resource was last updated.
      - `remote_data` object, nullable, required — Includes the data fetched from the remote system. Please be aware that including this in you scope config might violate other scopes that are set. Remote data always has the endpoint path that we got the data from as the top level key. For example, it could look like: `{ "/companies": { ... }}` This is not available on all plans. Reach out to Kombo if you need it.
      - `candidate` object, nullable, required
        - `id` string, required — The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing.
        - `remote_id` string, required — The raw ID of the object in the remote system. We don't recommend using this as a primary key on your side as it might sometimes be compromised of multiple identifiers if a system doesn't provide a clear primary key.
        - `first_name` string, nullable, required — First name of the candidate.
        - `last_name` string, nullable, required — Last name of the candidate.
        - `email_addresses` object[], nullable — A list of email addresses of the candidate with an optional type. If an email address is invalid, it will be filtered out.
          - `email_address` string, nullable
          - `type` string, nullable, required — Kombo exposes type information through this field. If we don't get any information from the tool, we will set this to `null`.
        - `phone_numbers` object[], nullable — A list of phone numbers of the candidate.
          - `phone_number` string, required
          - `type` string, nullable — Kombo exposes type information through this field. If we don't get any information from the tool, we will set this to `null`.
        - `social_media` object[], nullable — List of social media accounts of the candidate.
          - `link` string, nullable
          - `type` string, nullable
          - `username` string, nullable
        - `source` string, nullable, required — The hiring source of the candidate. If you're a job board or recruiting service, you can use this to validate which candidates applied through your service and ensure that the correct referral compensation is paid out.
        - `remote_url` string, uri, nullable, required — URL to the candidate profile in the source ATS system. When embedding this in your system, please consider that not for all ATS a dedicated candidate profile URL is available, so you might need to fall back to the application URL.
        - `tags` object[], required
          - `id` string, required — The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing.
          - `remote_id` string, nullable, required — The raw ID of the object in the remote system. We don't recommend using this as a primary key on your side as it might sometimes be compromised of multiple identifiers if a system doesn't provide a clear primary key.
          - `name` string, nullable, required
      - `current_stage` object, nullable, required
        - `id` string, required — The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing.
        - `remote_id` string, nullable, required — The raw ID of the object in the remote system. We don't recommend using this as a primary key on your side as it might sometimes be compromised of multiple identifiers if a system doesn't provide a clear primary key.
        - `name` string, nullable, required — The application stage name. For example, "Initial Screening".
        - `status` 'ACTIVE' | 'INACTIVE', nullable, required — Whether the application stage is active in the ATS. Inactive stages (also e.g., archived or hidden) may still be referenced by existing applications but are typically not part of the current hiring workflow.
        - `custom_fields` object, nullable, required — A key-value store of fields not covered by the schema. [Read more](/custom-fields)
        - `integration_fields` object[], required — An array of selected passthrough integration fields. [Read more](/integration-fields)
          - `id` string, required — The globally unique ID of this object.
          - `key` string, required — The key of the field in the remote system.
          - `type` 'DEFAULT' | 'CUSTOM', required — - `DEFAULT`: static fields in the remote system. - `CUSTOM`: fields that are created/editable by the user.
          - `value` unknown
          - `label` string, nullable, required — The label of the field. (not always available)
        - `index` integer, nullable, required
      - `job` object, nullable, required
        - `id` string, required — The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing.
        - `remote_id` string, required — The raw ID of the object in the remote system. We don't recommend using this as a primary key on your side as it might sometimes be compromised of multiple identifiers if a system doesn't provide a clear primary key.
        - `name` string, nullable, required — Title of the job.
      - `interviews` object[], required
        - `id` string, required — The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing.
        - `remote_id` string, nullable, required — The raw ID of the object in the remote system. We don't recommend using this as a primary key on your side as it might sometimes be compromised of multiple identifiers if a system doesn't provide a clear primary key.
        - `title` string, nullable, required — The title of the interview.
        - `starting_at` string, date-time, nullable, required — The start time of the interview.
        - `ending_at` string, date-time, nullable, required — The end time of the interview.
        - `location` object, nullable — Location of the interview.
          - `city` string, nullable
          - `country` string, nullable — Contains the ISO2 country code if possible. If not, it contains the original value.
          - `raw` string, nullable — If we have address data, this is filled with the raw address string.
          - `state` string, nullable
          - `street_1` string, nullable — If we can parse the address data, this field contains the first part of the street information.
          - `street_2` string, nullable
          - `zip_code` string, nullable
        - `canceled` boolean, nullable, required — Whether the interview was canceled or not. If we have no information, this field will be `null`.
      - `offers` object[], required
        - `id` string, required — The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing.
        - `remote_id` string, nullable, required — The raw ID of the object in the remote system. We don't recommend using this as a primary key on your side as it might sometimes be compromised of multiple identifiers if a system doesn't provide a clear primary key.
        - `status` 'ACCEPTED' | 'DECLINED' | 'SENT' | 'APPROVED' | 'DRAFT' | 'ABANDONED', nullable, required — The offer’s current status. The usual flow of statuses is as follows: `DRAFT` -> `APPROVED` -> `SENT` -> `ACCEPTED` or `DECLINED`. Please note that not all systems will expose all statuses. For example, most systems do not include the `APPROVED` status - `ACCEPTED`: The offer was accepted by the candidate. - `DECLINED`: The offer was declined by the candidate. - `SENT`: The offer was sent to the candidate. - `APPROVED`: The draft was approved. - `DRAFT`: The offer is a draft and has not yet been sent to the candidate. - `ABANDONED`: The offer has expired or is no longer valid and should not be considered.

## 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/revisions/149bf44faf1a/schema)