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

# Get jobs

`GET /ats/jobs`

Retrieve all jobs.

Visit our in-depth guides to learn more about:

- 🔄 [Getting updates of the data](/ats/features/implementation-guide/reading-jobs#getting-updates-of-the-data)
- ❗ [Handling failing syncs](/ats/features/implementation-guide/reading-jobs#handling-failing-syncs)
- 🔍 [Letting your customer choose which jobs to expose](/ats/features/implementation-guide/reading-jobs#let-your-customer-choose-which-jobs-to-expose-to-you)
- 🔗 [Matching jobs in your database to ATS jobs](/ats/features/implementation-guide/reading-jobs#match-jobs-in-your-database-to-ats-jobs)
- 🗑️ [Reacting to deleted/closed jobs](/ats/features/implementation-guide/reading-jobs#reacting-to-deleted-closed-jobs)

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 | | --- | --- | --- | | `stages` | ✓ Yes | ✗ No | | `screening_questions` | ✓ Yes | ✓ Yes | | `job_postings` | ✓ Yes | ✓ Yes | | `hiring_team` | ✓ Yes | ✗ No | _**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.
- `job_codes` string — Filter by a comma-separated list of job codes.
- `post_url` string — Filter by the `post_url` field. Can be used to find a job based on its public posting URL.
- `status` 'OPEN' | 'CLOSED' | 'DRAFT' | 'ARCHIVED' — **(⚠️ Deprecated - Use the `statuses` filter instead.)** Filter by the `status` field. Can be used to find a job based on its status.
- `statuses` string — Filter by a comma-separated list of `OPEN`, `CLOSED`, `DRAFT`, `ARCHIVED` Leave this blank to get results matching all values.
- `employment_types` string — Filter by a comma-separated list of `FULL_TIME`, `PART_TIME`, `CONTRACT`, `SEASONAL`, `INTERNSHIP` Leave this blank to get results matching all values.
- `visibilities` string — Filter by a comma-separated list of `PUBLIC`, `INTERNAL`, `UNLISTED`, `CONFIDENTIAL` Leave this blank to get results matching all values.
- `remote_created_after` string, date-time — Filter jobs by the day they were created in the remote system. This allows you to get jobs that were created on or after a certain day.
- `name_contains` string — Filter by the `name` field. Can be used to find a job by keywords present in the job name.

## Headers

- `X-Integration-Id` string, required

## Response `200`

GET /ats/jobs Positive response

- GetAtsJobsPositiveResponse
  - `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, 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.
      - `job_code` string, nullable, required — The human readable job code. Some systems expose this as the Requisition Code/ID.
      - `description` string, nullable, required — Description of the job. This field is usually returned as HTML.
      - `confidential` boolean, nullable, required — **(⚠️ Deprecated)** It makes more sense to store the visibility of a job in an enum. Therefore, we introduced the `visibility` enum on jobs.
      - `weekly_hours` number, double, nullable, required — The number of hours per week an employee is expected to work.
      - `employment_type` union — The type of employment contract. In rare cases where can't find a clear mapping, the original string is passed through.
        - 'FULL_TIME' | 'PART_TIME' | 'CONTRACT' | 'SEASONAL' | 'INTERNSHIP'
        - string — If we can't find a clear mapping: The original string passed through.
      - `status` union — The job's current status. *Note: For any checks (e.g., "can we publish this job?"), always evaluate both `status` and `visibility`. For example, a job can be `status=OPEN` with `visibility=INTERNAL`, meaning only existing employees can apply.* In rare cases where we can’t find a clear mapping, the original string is passed through.
        - 'OPEN' | 'CLOSED' | 'DRAFT' | 'ARCHIVED'
        - string — If we can't find a clear mapping: The original string passed through.
      - `visibility` union — Describes the visibility of the job: - `PUBLIC`: visible to everyone, published on a job board - `INTERNAL`: only visible to employees of the company itself - `UNLISTED`: anyone can apply but only if they have the link to it - `CONFIDENTIAL`: nobody can apply and it's only visible in the ATS to people who were invited to it *Note: For any checks (e.g., "can we publish this job?"), always evaluate both `status` and `visibility`.* In rare cases where we can’t find a clear mapping, the original string is passed through.
        - 'PUBLIC' | 'INTERNAL' | 'UNLISTED' | 'CONFIDENTIAL'
        - string — If we can't find a clear mapping: The original string passed through.
      - `category` string, nullable, required — The category of the job (often the job industry). The original string is passed through, for example "Information Technology", "Quality Assurance", "Marketing".
      - `department` string, nullable, required — The internal department or team the job belongs to. The original string is passed through, for example "IT/Operations", "Engineering - Platform", "Customer Success".
      - `post_url` string, nullable, required — The public job posting URL of the ATS itself. This can be used by external job boards to redirect applicants.
      - `experience_level` string, nullable, required — The role's seniority or experience level. The original string is passed through, for example "Mid-Senior Level", "5+ years", "Associate", "IC3".
      - `remote_work_status` union — Defines if the job supports remote work and if so, to what extent.
        - 'REMOTE' | 'HYBRID' | 'TEMPORARY' | 'ON_SITE'
        - string — If we can't find a clear mapping: The original string passed through.
      - `salary_amount` number, double, nullable, required — The salary amount in the given currency.
      - `salary_amount_from` number, double, nullable, required — The lower bound of the salary range.
      - `salary_amount_to` number, double, nullable, required — The upper bound of the salary range.
      - `salary_currency` string, nullable, required — Salary currency usually returned in [ISO 4217 currency codes](https://www.iso.org/iso-4217-currency-codes.html).
      - `salary_period` union — The period of time over which the salary amount is paid (not equal to the pay frequency). In rare cases where we can’t find a clear mapping, the original string is passed through.
        - 'YEAR' | 'MONTH' | 'TWO_WEEKS' | 'WEEK' | 'DAY' | 'HOUR'
        - string — If we can't find a clear mapping: The original string passed through.
      - `location` object, nullable — The location of the listed job.
        - `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
      - `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 job posting in the source ATS system.
      - `opened_at` string, date-time, nullable, required — YYYY-MM-DDTHH:mm:ss.sssZ
      - `closed_at` string, date-time, nullable, required — The date the job closed or is scheduled to close. A future value typically indicates the job remains open for applications until that date. Please use the `status` and `visibility` fields to determine if a job can be published.
      - `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.
      - `contact_id` string, nullable, required — **(⚠️ Deprecated)** The user ID of the contact person for this job. We strongly recommend using the new `hiring_team` property instead as it provides more complete and accurate information about the ATS users connected to a job.
      - `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.
      - `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.
      - `stages` object[], required — Application stages a candidate can be in for this particular job.
        - `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)
        - `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.
        - `index` integer, nullable — Numeric index following the order of the stages if they are ordered in the underlying tool.
      - `screening_questions` 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
        - `description` string, nullable, required — Additional instructions or context. Typically a short sentence, but sometimes a long detailed description (e.g., for EEO questions). May include HTML for extra formatting.
        - `format` union
          - object
            - `display_type` 'SINGLE_LINE' | 'MULTI_LINE' | 'EMAIL' | 'URL', nullable — If unavailable, we recommend displaying a single-line input.
            - `max_length` integer, nullable
            - `type` 'TEXT', required
          - object
            - `display_type` 'SLIDER' | 'FIELD', nullable
            - `max` number, double, nullable
            - `min` number, double, nullable
            - `type` 'NUMBER', required
          - object
            - `accepted_mime_types` string[], nullable
            - `max_file_size_bytes` integer, nullable
            - `type` 'FILE', required
          - object
            - `display_type` 'DROPDOWN' | 'RADIO', nullable
            - `options` object[], required
              - …
            - `type` 'SINGLE_SELECT', required
          - object
            - `type` 'BOOLEAN', required
          - object
            - `type` 'DATE', required
          - object
            - `options` object[], required
              - …
            - `type` 'MULTI_SELECT', required
          - object
            - `type` 'INFORMATION', required — This is just a text block.
          - object
            - `raw_question` unknown
            - `type` 'UNKNOWN', required — When we're not able to map a specific question type yet, we will return this type. Every `UNKNOWN` question will also be parsed and unified by us at some point.
        - `category` 'EEO' | 'DEMOGRAPHIC', nullable, required — The category of the screening question (default `null`). "EEO" questions are related to Equal Employment Opportunity (e.g. "What is your veteran status?"), while "DEMOGRAPHIC" questions are for other diversity and demographic data collection.
        - `index` integer, nullable
        - `required` boolean, nullable, required
        - `precondition_question_id` string, nullable — The Kombo ID of another screening question. Only display this question if the specified "precondition question" is answered with one of the values in `precondition_options`.
        - `precondition_options` union — Where the screening question specified by `precondition_question_id` is of type `MULTI_SELECT` or `SINGLE_SELECT`, this is an array of Kombo IDs describing the valid options. If the question is of type `BOOLEAN`, this is an array containing either `true` or `false`.
          - string[]
          - boolean[]
      - `job_postings` 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 job posting’s title.
        - `description_html` string, nullable, required — The job posting’s description in HTML format.
        - `status` 'ACTIVE' | 'INACTIVE' | 'DRAFT', nullable, required — The job posting’s current status.
        - `visibility` 'PUBLIC' | 'INTERNAL' | 'UNLISTED', nullable, required
        - `url` string, nullable, required — The public URL to the job posting on the ATS platform.
        - `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.
      - `hiring_team` object[], required — The hiring team allows you to sync users into your system who can access the job and its applications.
        - `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.
        - `first_name` string, nullable, required — First name of the user.
        - `last_name` string, nullable, required — Last name of the user.
        - `email` string, nullable — Email of the user. If the email address is invalid, it will be set to null.
        - `hiring_team_roles` string[], required — **(⚠️ Deprecated - Use `job_roles` to access the full list of job roles (including custom labels and unmapped roles).)** Array of the roles of the user for this specific job. Example: ["RECRUITER", "HIRING_MANAGER"].
        - `job_roles` object[], required — Roles assigned to this user for this job. Visit our in-depth guide about [roles](/ats/features/roles) to learn more. Use `system_roles` on the `/v1/ats/users` endpoint for system-wide roles.
          - `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.
          - `remote_label` string, nullable, required — The label of the role.
          - `unified_type` 'HIRING_MANAGER' | 'RECRUITER' | 'COORDINATOR' | 'SOURCER' | 'INTERVIEWER' | 'ADMIN', nullable, required — Unified role type if Kombo can map it.
          - `scope` 'JOB', required — Roles that apply at the job level.

## 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)