> ## Documentation Index > Fetch the complete documentation index at: https://docs.kombo.dev/llms.txt > Use this file to discover all available pages before exploring further. # Get jobs > Retrieve all jobs. This feature is currently available for the following integrations:

You'd like to see this feature for another integration? Please reach out! We're always happy to discuss extending our coverage. 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)` ## OpenAPI ````yaml GET /ats/jobs openapi: 3.1.0 info: title: Kombo API version: 1.0.0 servers: - url: https://api.kombo.dev/v1 description: Kombo EU API - url: https://api.us.kombo.dev/v1 description: Kombo US API security: - ApiKey: [] tags: - name: General - name: Kombo Connect description: >- Endpoints for Kombo Connect, our end-user-facing flow for setting up new integrations. - name: Unified HRIS API description: Unified endpoints to access all the HR concepts you might need. - name: Unified ATS API description: Unified endpoints to access all the ATS concepts you might need. - name: Unified ATS (Assessment & Background Check) API description: >- Unified endpoints to operate Assessments and Background Checks for many applicant tracking systems. - name: Unified LMS API description: Unified endpoints to access all the LMS concepts you might need. - name: AI Apply description: Endpoints for AI-powered job application features. - name: Custom Endpoints description: Custom integration-specific endpoints. paths: /ats/jobs: get: tags: - Unified ATS API summary: Get jobs description: >- Retrieve all jobs. This feature is currently available for the following integrations:

You'd like to see this feature for another integration? Please reach out! We're always happy to discuss extending our coverage. 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)` operationId: GetAtsJobs parameters: - in: header name: X-Integration-Id schema: type: string description: ID of the integration you want to interact with. example: join:HWUTwvyx2wLoSUHphiWVrp28 required: true - name: cursor in: query required: false description: >- An optional cursor string used for pagination. This can be retrieved from the `next` property of the previous page response. schema: $ref: '#/components/schemas/GetAtsJobsParameterCursor' - name: page_size in: query required: false description: The number of results to return per page. Maximum is 250. schema: $ref: '#/components/schemas/GetAtsJobsParameterPageSize' - name: updated_after in: query required: false description: >- 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 | ✗ No | | `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._ schema: $ref: '#/components/schemas/GetAtsJobsParameterUpdatedAfter' - name: include_deleted in: query required: false description: >- By default, deleted entries are not returned. Use the `include_deleted` query param to include deleted entries too. schema: $ref: '#/components/schemas/GetAtsJobsParameterIncludeDeleted' - name: ignore_unsupported_filters in: query required: false description: >- When set to `true`, filters targeting fields not supported by this integration will be ignored instead of filtering out all results. schema: $ref: '#/components/schemas/GetAtsJobsParameterIgnoreUnsupportedFilters' - name: ids in: query required: false description: >- Filter by a comma-separated list of IDs such as `222k7eCGyUdgt2JWZDNnkDs3,B5DVmypWENfU6eMe6gYDyJG3`. schema: $ref: '#/components/schemas/GetAtsJobsParameterIds' - name: remote_ids in: query required: false description: Filter by a comma-separated list of remote IDs. schema: $ref: '#/components/schemas/GetAtsJobsParameterRemoteIds' - name: job_codes in: query required: false description: Filter by a comma-separated list of job codes. schema: $ref: '#/components/schemas/GetAtsJobsParameterJobCodes' - name: post_url in: query required: false description: >- Filter by the `post_url` field. Can be used to find a job based on its public posting URL. schema: $ref: '#/components/schemas/GetAtsJobsParameterPostUrl' - name: status in: query required: false description: >- **(⚠️ Deprecated - Use the `statuses` filter instead.)** Filter by the `status` field. Can be used to find a job based on its status. schema: $ref: '#/components/schemas/GetAtsJobsParameterStatus' deprecated: true - name: statuses in: query required: false description: >- Filter by a comma-separated list of `OPEN`, `CLOSED`, `DRAFT`, `ARCHIVED` Leave this blank to get results matching all values. schema: $ref: '#/components/schemas/GetAtsJobsParameterStatuses' - name: employment_types in: query required: false description: >- Filter by a comma-separated list of `FULL_TIME`, `PART_TIME`, `CONTRACT`, `SEASONAL`, `INTERNSHIP` Leave this blank to get results matching all values. schema: $ref: '#/components/schemas/GetAtsJobsParameterEmploymentTypes' - name: visibilities in: query required: false description: >- Filter by a comma-separated list of `PUBLIC`, `INTERNAL`, `UNLISTED`, `CONFIDENTIAL` Leave this blank to get results matching all values. schema: $ref: '#/components/schemas/GetAtsJobsParameterVisibilities' - name: remote_created_after in: query required: false description: >- 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. schema: $ref: '#/components/schemas/GetAtsJobsParameterRemoteCreatedAfter' - name: name_contains in: query required: false description: >- Filter by the `name` field. Can be used to find a job by keywords present in the job name. schema: $ref: '#/components/schemas/GetAtsJobsParameterNameContains' responses: '200': description: GET /ats/jobs Positive response content: application/json: schema: $ref: '#/components/schemas/GetAtsJobsPositiveResponse' examples: example1: value: status: success data: next: >- eyJwYWdlIjoxMiwibm90ZSI6InRoaXMgaXMganVzdCBhbiBleGFtcGxlIGFuZCBub3QgcmVwcmVzZW50YXRpdmUgZm9yIGEgcmVhbCBjdXJzb3IhIn0= results: - id: H5daSm8e85Dmvmne3wLeCPhX remote_id: '32' name: Backend Engineer job_code: BE-2021-01 description: >-

Kombo is hiring engineers! If you are reading this and you are located in Berlin, Germany, feel free to contact us about this position.

confidential: false weekly_hours: 37 employment_type: FULL_TIME status: OPEN visibility: PUBLIC category: Technical Job department: Engineering post_url: https://jobs.example.com/post/159829112 experience_level: Mid-Senior remote_work_status: HYBRID salary_amount: 4200 salary_amount_from: null salary_amount_to: null salary_currency: EUR salary_period: MONTH location: city: Berlin country: DE raw: Berlin, Germany state: Berlin street_1: Lohmühlenstraße 65 street_2: null zip_code: '12435' custom_fields: {} integration_fields: [] remote_url: https://app.greenhouse.io/jobs/32 opened_at: '2022-08-07T14:01:29.196Z' closed_at: null remote_created_at: '2022-08-07T14:01:29.196Z' remote_updated_at: '2022-08-07T14:01:29.196Z' contact_id: 6gT2yLMBEipd3zpezATv3Rhu remote_data: null changed_at: '2022-08-07T14:01:29.196Z' remote_deleted_at: null stages: - id: 5J7L4b48wBfffYwek9Az9pkM remote_id: '32' name: Initial Screening remote_data: null index: 0 screening_questions: - id: 26vafvWSRmbhNcxJYqjCzuJg remote_id: 48b4d36a-1d4b-4c50-ada7-9519078e65b4 title: Which is your primary programming language? description: >- Please enter the language you are most comfortable with. format: display_type: SINGLE_LINE max_length: null type: TEXT category: null index: 0 required: true precondition_question_id: 4ZVteCSSgDw3BdwGzcQqGEPk precondition_options: - 7qd5qjPwDHarsMLFMGzXYG1K job_postings: - id: 26vafvWSRmbhNcxJYqjCzuJg remote_id: 48b4d36a-1d4b-4c50-ada7-9519078e65b4 title: Frontend Engineer description_html:

We are looking for a Frontend Engineer.

status: ACTIVE visibility: PUBLIC url: https://jobs.example.com/post/159829112 remote_data: null hiring_team: - id: 26vafvWSRmbhNcxJYqjCzuJg remote_id: '32' first_name: John last_name: Doe email: john.doe@kombo.dev hiring_team_roles: - RECRUITER job_roles: - remote_id: '32' remote_label: Hiring Manager scope: JOB unified_type: HIRING_MANAGER default: $ref: '#/components/responses/ErrorResponseATS' x-codeSamples: - lang: python label: GetAtsJobs source: |- from kombo import Kombo with Kombo( integration_id="workday:HWUTwvyx2wLoSUHphiWVrp28", api_key="", ) as k_client: res = k_client.ats.get_jobs(page_size=100, include_deleted=False, ignore_unsupported_filters=False) while res is not None: # Handle items res = res.next() - lang: typescript label: GetAtsJobs source: |- import { Kombo } from "@kombo-api/sdk"; const kombo = new Kombo({ integration_id: "workday:HWUTwvyx2wLoSUHphiWVrp28", api_key: "", }); async function run() { const result = await kombo.ats.getJobs({}); for await (const page of result) { console.log(page); } } run(); - lang: ruby label: GetAtsJobs source: >- require 'kombo' Models = ::Kombo::Models s = ::Kombo::Kombo.new( integration_id: 'workday:HWUTwvyx2wLoSUHphiWVrp28', security: Models::Shared::Security.new( api_key: '' ) ) res = s.ats.get_jobs(page_size: 100, include_deleted: false, ignore_unsupported_filters: false) unless res.get_ats_jobs_positive_response.nil? # handle response end components: schemas: GetAtsJobsParameterCursor: type: string description: >- An optional cursor string used for pagination. This can be retrieved from the `next` property of the previous page response. GetAtsJobsParameterPageSize: type: integer format: int64 minimum: 1 maximum: 250 default: 100 description: The number of results to return per page. Maximum is 250. GetAtsJobsParameterUpdatedAfter: description: >- 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 | ✗ No | | `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._ type: string format: date-time pattern: ^\d{4}-\d{2}-\d{2}(T\d{2}:\d{2}:\d{2}(\.\d+)?)?Z?$ externalDocs: url: >- https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString GetAtsJobsParameterIncludeDeleted: type: string enum: - 'true' - 'false' default: 'false' description: >- By default, deleted entries are not returned. Use the `include_deleted` query param to include deleted entries too. GetAtsJobsParameterIgnoreUnsupportedFilters: type: string enum: - 'true' - 'false' default: 'false' description: >- When set to `true`, filters targeting fields not supported by this integration will be ignored instead of filtering out all results. GetAtsJobsParameterIds: type: string description: >- Filter by a comma-separated list of IDs such as `222k7eCGyUdgt2JWZDNnkDs3,B5DVmypWENfU6eMe6gYDyJG3`. GetAtsJobsParameterRemoteIds: type: string description: Filter by a comma-separated list of remote IDs. GetAtsJobsParameterJobCodes: type: string description: Filter by a comma-separated list of job codes. GetAtsJobsParameterPostUrl: type: string description: >- Filter by the `post_url` field. Can be used to find a job based on its public posting URL. GetAtsJobsParameterStatus: type: string enum: - OPEN - CLOSED - DRAFT - ARCHIVED description: >- **(⚠️ Deprecated - Use the `statuses` filter instead.)** Filter by the `status` field. Can be used to find a job based on its status. deprecated: true GetAtsJobsParameterStatuses: type: string description: >- Filter by a comma-separated list of `OPEN`, `CLOSED`, `DRAFT`, `ARCHIVED` Leave this blank to get results matching all values. GetAtsJobsParameterEmploymentTypes: type: string description: >- Filter by a comma-separated list of `FULL_TIME`, `PART_TIME`, `CONTRACT`, `SEASONAL`, `INTERNSHIP` Leave this blank to get results matching all values. GetAtsJobsParameterVisibilities: type: string description: >- Filter by a comma-separated list of `PUBLIC`, `INTERNAL`, `UNLISTED`, `CONFIDENTIAL` Leave this blank to get results matching all values. GetAtsJobsParameterRemoteCreatedAfter: description: >- 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. type: string format: date-time pattern: ^\d{4}-\d{2}-\d{2}(T\d{2}:\d{2}:\d{2}(\.\d+)?)?Z?$ externalDocs: url: >- https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString GetAtsJobsParameterNameContains: type: string description: >- Filter by the `name` field. Can be used to find a job by keywords present in the job name. GetAtsJobsPositiveResponse: type: object properties: status: type: string const: success data: type: object properties: next: type: - string - 'null' description: >- 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: type: array items: type: object properties: id: type: string description: >- The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing. remote_id: type: string description: >- 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: type: - string - 'null' description: Title of the job. job_code: type: - string - 'null' description: >- The human readable job code. Some systems expose this as the Requisition Code/ID. description: type: - string - 'null' description: >- Description of the job. This field is usually returned as HTML. confidential: type: - boolean - 'null' description: >- **(⚠️ Deprecated)** It makes more sense to store the visibility of a job in an enum. Therefore, we introduced the `visibility` enum on jobs. deprecated: true weekly_hours: type: - number - 'null' format: double minimum: -1.7976931348623157e+308 description: >- The number of hours per week an employee is expected to work. employment_type: anyOf: - type: string enum: - FULL_TIME - PART_TIME - CONTRACT - SEASONAL - INTERNSHIP - type: string description: >- If we can't find a clear mapping: The original string passed through. - type: 'null' description: >- The type of employment contract. In rare cases where can't find a clear mapping, the original string is passed through. status: anyOf: - type: string enum: - OPEN - CLOSED - DRAFT - ARCHIVED - type: string description: >- If we can't find a clear mapping: The original string passed through. - type: 'null' description: >- 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. visibility: anyOf: - type: string enum: - PUBLIC - INTERNAL - UNLISTED - CONFIDENTIAL - type: string description: >- If we can't find a clear mapping: The original string passed through. - type: 'null' description: >- 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. category: type: - string - 'null' description: >- The category of the job (often the job industry). The original string is passed through, for example "Information Technology", "Quality Assurance", "Marketing". department: type: - string - 'null' description: >- 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: type: - string - 'null' description: >- The public job posting URL of the ATS itself. This can be used by external job boards to redirect applicants. experience_level: type: - string - 'null' description: >- 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: anyOf: - type: string enum: - REMOTE - HYBRID - TEMPORARY - ON_SITE - type: string description: >- If we can't find a clear mapping: The original string passed through. - type: 'null' description: >- Defines if the job supports remote work and if so, to what extent. salary_amount: type: - number - 'null' format: double minimum: -1.7976931348623157e+308 description: The salary amount in the given currency. salary_amount_from: type: - number - 'null' format: double minimum: -1.7976931348623157e+308 description: The lower bound of the salary range. salary_amount_to: type: - number - 'null' format: double minimum: -1.7976931348623157e+308 description: The upper bound of the salary range. salary_currency: type: - string - 'null' description: >- Salary currency usually returned in [ISO 4217 currency codes](https://www.iso.org/iso-4217-currency-codes.html). salary_period: anyOf: - type: string enum: - YEAR - MONTH - TWO_WEEKS - WEEK - DAY - HOUR - type: string description: >- If we can't find a clear mapping: The original string passed through. - type: 'null' description: >- 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. location: type: - object - 'null' properties: city: type: - string - 'null' country: type: - string - 'null' description: >- Contains the ISO2 country code if possible. If not, it contains the original value. raw: type: - string - 'null' description: >- If we have address data, this is filled with the raw address string. state: type: - string - 'null' street_1: type: - string - 'null' description: >- If we can parse the address data, this field contains the first part of the street information. street_2: type: - string - 'null' zip_code: type: - string - 'null' description: The location of the listed job. custom_fields: type: - object - 'null' additionalProperties: true description: >- A key-value store of fields not covered by the schema. [Read more](/custom-fields) integration_fields: type: array items: type: object properties: id: type: string description: The globally unique ID of this object. key: type: string description: The key of the field in the remote system. type: type: string enum: - DEFAULT - CUSTOM description: >- - `DEFAULT`: static fields in the remote system. - `CUSTOM`: fields that are created/editable by the user. value: type: 'null' description: The field's value. label: type: - string - 'null' description: The label of the field. (not always available) required: - id - key - type - label description: >- An array of selected passthrough integration fields. [Read more](/integration-fields) examples: - - id: 5NVFhMpB9Ah6by44tzNjZLyE key: firstName type: DEFAULT value: Frank label: First Name - id: 8nuajYpoRd5GnxEQaaWKUDYQ key: customTshirtSize type: CUSTOM value: XL label: T-Shirt Size remote_url: type: - string - 'null' format: uri description: URL to the job posting in the source ATS system. opened_at: description: YYYY-MM-DDTHH:mm:ss.sssZ type: - string - 'null' format: date-time externalDocs: url: >- https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString closed_at: description: >- 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. type: - string - 'null' format: date-time externalDocs: url: >- https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString remote_created_at: description: >- The date and time the object was created in the remote system. type: - string - 'null' format: date-time externalDocs: url: >- https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString remote_updated_at: description: >- A timestamp retrieved from the remote system, describing when the resource was last updated. type: - string - 'null' format: date-time externalDocs: url: >- https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString contact_id: type: - string - 'null' description: >- **(⚠️ 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. deprecated: true remote_data: type: - object - 'null' additionalProperties: true description: >- 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: description: >- 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. type: string format: date-time externalDocs: url: >- https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString remote_deleted_at: description: >- 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. type: - string - 'null' format: date-time externalDocs: url: >- https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString stages: type: array items: type: object properties: id: type: string description: >- The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing. remote_id: type: - string - 'null' description: >- 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: type: - string - 'null' description: >- The application stage name. For example, "Initial Screening". remote_data: type: - object - 'null' additionalProperties: true description: >- 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: type: - integer - 'null' format: int64 description: >- Numeric index following the order of the stages if they are ordered in the underlying tool. required: - id - remote_id - name - remote_data examples: - id: 5J7L4b48wBfffYwek9Az9pkM remote_id: '32' name: Initial Screening remote_data: null index: 0 description: >- Application stages a candidate can be in for this particular job. screening_questions: type: array items: type: object properties: id: type: string description: >- The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing. remote_id: type: - string - 'null' description: >- 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: type: - string - 'null' description: type: - string - 'null' description: >- 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: anyOf: - type: object properties: display_type: type: - string - 'null' enum: - SINGLE_LINE - MULTI_LINE - EMAIL - URL description: >- If unavailable, we recommend displaying a single-line input. max_length: type: - integer - 'null' format: int64 type: type: string const: TEXT required: - type - type: object properties: display_type: type: - string - 'null' enum: - SLIDER - FIELD default: FIELD max: type: - number - 'null' format: double minimum: -1.7976931348623157e+308 min: type: - number - 'null' format: double minimum: -1.7976931348623157e+308 type: type: string const: NUMBER required: - type - type: object properties: accepted_mime_types: type: - array - 'null' items: type: string max_file_size_bytes: type: - integer - 'null' format: int64 type: type: string const: FILE required: - type - type: object properties: display_type: type: - string - 'null' enum: - DROPDOWN - RADIO options: type: array items: type: object properties: id: type: string description: >- The Kombo ID of this question option. Use this ID to specify the answer to this question. remote_id: type: - string - 'null' description: >- ID in the connected ATS. This might be null as some systems only use the name to identify the option. name: type: string description: Content of the question option. required: - id - name type: type: string const: SINGLE_SELECT required: - options - type - type: object properties: type: type: string const: BOOLEAN required: - type - type: object properties: type: type: string const: DATE required: - type - type: object properties: options: type: array items: type: object properties: id: type: string description: >- The Kombo ID of this question option. Use this ID to specify the answer to this question. remote_id: type: - string - 'null' description: >- ID in the connected ATS. This might be null as some systems only use the name to identify the option. name: type: string description: Content of the question option. required: - id - name type: type: string const: MULTI_SELECT required: - options - type - type: object properties: type: type: string const: INFORMATION description: This is just a text block. required: - type - type: object properties: raw_question: description: >- We pass the original question data along so you can handle it. type: type: string const: UNKNOWN description: >- 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. required: - type - type: 'null' category: type: - string - 'null' enum: - EEO - DEMOGRAPHIC description: >- 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: type: - integer - 'null' format: int64 required: type: - boolean - 'null' precondition_question_id: type: - string - 'null' minLength: 24 maxLength: 24 pattern: ^[1-9A-HJ-NP-Za-km-z]+$ description: >- 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: anyOf: - type: array items: type: string minLength: 24 maxLength: 24 pattern: ^[1-9A-HJ-NP-Za-km-z]+$ - type: array items: type: boolean - type: 'null' default: null description: >- 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`. required: - id - remote_id - title - description - category - required examples: - id: 26vafvWSRmbhNcxJYqjCzuJg remote_id: 48b4d36a-1d4b-4c50-ada7-9519078e65b4 title: Which is your primary programming language? description: >- Please enter the language you are most comfortable with. format: display_type: SINGLE_LINE max_length: null type: TEXT category: null index: 0 required: true precondition_question_id: 4ZVteCSSgDw3BdwGzcQqGEPk precondition_options: - 7qd5qjPwDHarsMLFMGzXYG1K job_postings: type: array items: type: object properties: id: type: string description: >- The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing. remote_id: type: - string - 'null' description: >- 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: type: - string - 'null' description: The job posting’s title. description_html: type: - string - 'null' description: The job posting’s description in HTML format. status: type: - string - 'null' enum: - ACTIVE - INACTIVE - DRAFT description: The job posting’s current status. visibility: type: - string - 'null' enum: - PUBLIC - INTERNAL - UNLISTED url: type: - string - 'null' description: >- The public URL to the job posting on the ATS platform. remote_data: type: - object - 'null' additionalProperties: true description: >- 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. required: - id - remote_id - title - description_html - status - visibility - url - remote_data examples: - id: 26vafvWSRmbhNcxJYqjCzuJg remote_id: 48b4d36a-1d4b-4c50-ada7-9519078e65b4 title: Frontend Engineer description_html:

We are looking for a Frontend Engineer.

status: ACTIVE visibility: PUBLIC url: https://jobs.example.com/post/159829112 remote_data: null hiring_team: type: array items: type: object properties: id: type: string description: >- The globally unique ID of this object generated by Kombo. We recommend using this as a stable primary key for syncing. remote_id: type: - string - 'null' description: >- 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: type: - string - 'null' description: First name of the user. last_name: type: - string - 'null' description: Last name of the user. email: type: - string - 'null' pattern: >- ^(?!\.)(?!.*\.\.)([\w'+-.]*)[\w+-]@([\da-z][\da-z-]*\.)+[a-z]{2,}$ description: >- Email of the user. If the email address is invalid, it will be set to null. hiring_team_roles: type: array items: type: string enum: - RECRUITER - HIRING_MANAGER - COORDINATOR - SOURCER - INTERVIEWER examples: - RECRUITER description: >- **(⚠️ Deprecated - Use `job_roles` to access the full list of job roles.)** Array of the roles of the user for this specific job. Currently only `RECRUITER` and `HIRING_MANAGER` are mapped into our unified schema. deprecated: true job_roles: type: array items: type: object properties: remote_id: type: - string - 'null' description: >- 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: type: - string - 'null' description: The label of the role. scope: type: - string - 'null' enum: - SYSTEM - JOB examples: - JOB description: >- Whether the role applies globally or is scoped to a specific job. unified_type: type: - string - 'null' enum: - HIRING_MANAGER - RECRUITER - COORDINATOR - SOURCER - INTERVIEWER - ADMIN description: Unified role type if Kombo can map it. required: - remote_id - remote_label - scope - unified_type examples: - remote_id: '32' remote_label: Hiring Manager scope: JOB unified_type: HIRING_MANAGER - remote_id: '32' remote_label: Hiring Manager scope: JOB unified_type: HIRING_MANAGER description: >- 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. required: - id - remote_id - first_name - last_name - hiring_team_roles - job_roles description: >- The hiring team allows you to sync users into your system who can access the job and its applications. required: - id - remote_id - name - job_code - description - confidential - weekly_hours - category - department - post_url - experience_level - salary_amount - salary_amount_from - salary_amount_to - salary_currency - custom_fields - integration_fields - remote_url - opened_at - closed_at - remote_created_at - remote_updated_at - contact_id - remote_data - changed_at - remote_deleted_at - stages - screening_questions - job_postings - hiring_team required: - next - results examples: - next: >- eyJwYWdlIjoxMiwibm90ZSI6InRoaXMgaXMganVzdCBhbiBleGFtcGxlIGFuZCBub3QgcmVwcmVzZW50YXRpdmUgZm9yIGEgcmVhbCBjdXJzb3IhIn0= results: - id: H5daSm8e85Dmvmne3wLeCPhX remote_id: '32' name: Backend Engineer job_code: BE-2021-01 description: >-

Kombo is hiring engineers! If you are reading this and you are located in Berlin, Germany, feel free to contact us about this position.

confidential: false weekly_hours: 37 employment_type: FULL_TIME status: OPEN visibility: PUBLIC category: Technical Job department: Engineering post_url: https://jobs.example.com/post/159829112 experience_level: Mid-Senior remote_work_status: HYBRID salary_amount: 4200 salary_amount_from: null salary_amount_to: null salary_currency: EUR salary_period: MONTH location: city: Berlin country: DE raw: Berlin, Germany state: Berlin street_1: Lohmühlenstraße 65 street_2: null zip_code: '12435' custom_fields: {} integration_fields: [] remote_url: https://app.greenhouse.io/jobs/32 opened_at: '2022-08-07T14:01:29.196Z' closed_at: null remote_created_at: '2022-08-07T14:01:29.196Z' remote_updated_at: '2022-08-07T14:01:29.196Z' contact_id: 6gT2yLMBEipd3zpezATv3Rhu remote_data: null changed_at: '2022-08-07T14:01:29.196Z' remote_deleted_at: null stages: - id: 5J7L4b48wBfffYwek9Az9pkM remote_id: '32' name: Initial Screening remote_data: null index: 0 screening_questions: - id: 26vafvWSRmbhNcxJYqjCzuJg remote_id: 48b4d36a-1d4b-4c50-ada7-9519078e65b4 title: Which is your primary programming language? description: Please enter the language you are most comfortable with. format: display_type: SINGLE_LINE max_length: null type: TEXT category: null index: 0 required: true precondition_question_id: 4ZVteCSSgDw3BdwGzcQqGEPk precondition_options: - 7qd5qjPwDHarsMLFMGzXYG1K job_postings: - id: 26vafvWSRmbhNcxJYqjCzuJg remote_id: 48b4d36a-1d4b-4c50-ada7-9519078e65b4 title: Frontend Engineer description_html:

We are looking for a Frontend Engineer.