---
title: "Create candidate"
method: POST
path: "/ats/candidates"
tags: ["Unified ATS API"]
---

# Create candidate

`POST /ats/candidates`

Create a new candidate and application for the specified job.

<Warning>
      **We recommend using the [Create application](/ats/v1/post-jobs-job-id-applications) endpoint instead.**

      We realized that in practice it was always more about creating _applications_ instead of _candidates_, so we created a new, more aptly named one that you should use instead: [Create application](/ats/v1/post-jobs-job-id-applications)

      Using it also has the benefit that we return the newly created applicant at the root level, so you can easily store its ID.
    </Warning>

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

### Example Request Body

```json
{
  "candidate": {
    "first_name": "Frank",
    "last_name": "Doe",
    "company": "Acme Inc.",
    "title": "Head of Integrations",
    "email_address": "frank.doe@example.com",
    "phone_number": "+1-541-754-3010",
    "gender": "MALE",
    "salary_expectations": {
      "amount": 100000,
      "period": "YEAR"
    },
    "availability_date": "2021-01-01",
    "location": {
      "city": "New York",
      "country": "US",
      "state": "NY"
    },
    "social_links": [
      {
        "url": "https://www.linkedin.com/in/frank-doe-123456789/"
      },
      {
        "url": "https://twitter.com/frankdoe"
      }
    ]
  },
  "application": {
    "job_id": "BDpgnpZ148nrGh4mYHNxJBgx",
    "stage_id": "8x3YKRDcuRnwShdh96ShBNn1"
  },
  "attachments": [
    {
      "name": "Frank Doe CV.txt",
      "data": "SGkgdGhlcmUsIEtvbWJvIGlzIGN1cnJlbnRseSBoaXJpbmcgZW5naW5lZXJzIHRoYXQgbG92ZSB0byB3b3JrIG9uIGRldmVsb3BlciBwcm9kdWN0cy4=",
      "type": "CV",
      "content_type": "text/plain"
    }
  ],
  "screening_question_answers": [
    {
      "question_id": "3phFBNXRweGnDmsU9o2vdPuQ",
      "answer": "Yes"
    },
    {
      "question_id": "EYJjhMQT3LtVKXnTbnRT8s6U",
      "answer": [
        "GUzE666zfyjeoCJX6A8n7wh6",
        "5WPHzzKAv8cx97KtHRUV96U8",
        "7yZfKGzWigXxxRTygqAfHvyE"
      ]
    }
  ],
  "remote_fields": {}
}
```

## Headers

- `X-Integration-Id` string, required

## Request body

- PostAtsCandidatesRequestBody
  - `candidate` object, required
    - `first_name` string, required — The first name of the candidate.
    - `last_name` string, required — The last name of the candidate.
    - `email_address` string, email, required — The primary email address this application will be created with.
    - `additional_email_addresses` object[]
      - `type` 'PERSONAL' | 'WORK' | 'OTHER', required
      - `email_address` string, email, required
    - `company` string — The company where the candidate is currently working.
    - `title` string — The current job title of the candidate.
    - `phone_number` string — The phone number of the candidate.
    - `additional_phone_numbers` object[]
      - `type` 'PERSONAL' | 'WORK' | 'OTHER', required
      - `phone_number` string, required
    - `location` object — The location of the candidate.
      - `city` string
      - `country` string, required — The uppercase two-letter ISO country (e.g., `DE`). For systems that use codes in formats other than `ISO 3166-1 alpha-2`, Kombo transforms the ISO Codes to the appropriate value.
      - `state` string
      - `street_1` string
      - `zip_code` string
    - `gender` 'MALE' | 'FEMALE' | 'OTHER' — The gender of the candidate. Must be one of `MALE`, `FEMALE`, or `OTHER`.
    - `availability_date` string, date-time — The date the candidate is available to start working.
    - `salary_expectations` object — The salary expectations of the applicant. We will automatically convert the amount to a format that is suitable for the ATS you are using. For example, if you are using monthly salary expectations, we will convert the amount to a yearly salary if the ATS expects yearly salary expectations.
      - `period` 'MONTH' | 'YEAR', required — The period of the salary expectations. Must be one of `MONTH` or `YEAR`.
      - `amount` number, double, required — The amount of the salary expectations.
    - `social_links` object[] — A list of social media links of the candidate. The links must be valid URLs.
      - `url` string, uri, required
  - `application` object, required — Currently, every candidate has one application. If you are interested in talent pools, please contact Kombo.
    - `job_id` string, required — The Kombo ID or Remote ID of the Job this candidate should apply to. If you want to use the ID of the integrated system (remote_id) you need to prefix the ID with "remote:". You can use the remote ID if you do not want to sync jobs.
    - `stage_id` string — Stage this candidate should be in. If left out, the default stage for this job will be used.
  - `screening_question_answers` object[] — Array of answers to screening questions. Currently, not all question types are supported, and unsupported ones will not be submitted. The available questions for a job can be retrieved from the get jobs endpoint. The answers will be validated based on the format of the questions. Make sure to follow this schema to avoid errors.
    - `question_id` string, required — ID of the question returned by the Kombo API. We'll report a warning in the logs if the question can't be found on the job.
    - `answer` union, required — Answer to a question. This will be validated based on the question format and throw an error if the answer is invalid. Here is a description of each question type and the required answer format: `TEXT` - Simply provide a "string" answer. `SINGLE_SELECT` - Provide the ID of the answer as a string. `MULTI_SELECT` - Provide a string array containing the question IDs of the selected options. `BOOLEAN` - Either `true` or `false`. `NUMBER` - A number. `DATE` - Provide the answer as an ISO 8601 date string. `FILE` - Please select Option 6 in the dropdown above to see the required format.
      - string — Answer to a `TEXT` question or the option ID of the answer to a `SINGLE_SELECT` question.
      - boolean — Answer to a `BOOLEAN` question.
      - number, double — Answer to a `NUMBER` question.
      - string[] — Answer to a `MULTI_SELECT` question. The array elements are the IDs of the selected options.
      - string, date-time — Answer to a `DATE` question as an ISO 8601 date string.
      - object — Answer to a `FILE` question.
        - `name` string, required — File name of the file you want to upload. We recommend providing something human-readable with a valid file extension (like `Resume.pdf`), as this might be shown in your customer's system.
        - `content_type` string — Content/MIME type of the file (e.g., `application/pdf`). If you provide `data`, this is required. If you provide `data_url`, this is optional and we'll attempt to use the `Content-Type` header of the response. **Note:** Please validate that the content type you provide is actually meaningful (and not something generic like [`application/octet-stream`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/MIME_types#applicationoctet-stream)). Especially when using object storage (like AWS S3), it's easy to accidentally discard the content types of user-provided files, so make sure to explicitly persist them when processing uploads from your users (see guides for [AWS](https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingMetadata.html#SysMetadata), [Google Cloud](https://cloud.google.com/storage/docs/metadata#content-type), and [Azure](https://learn.microsoft.com/en-us/rest/api/storageservices/put-blob#request-headers-all-blob-types)).
        - `data_url` string, uri — URL to the file you want to upload that can be accessed without authentication headers. We will download the content immediately when receiving the request, so the URL can be short-lived. If you're using an object storage provider (like AWS S3), we strongly recommend providing a signed URL for secure access (see guides for [AWS](https://docs.aws.amazon.com/AmazonS3/latest/userguide/ShareObjectPreSignedURL.html), [Google Cloud](https://cloud.google.com/storage/docs/access-control/signed-urls), and [Azure](https://learn.microsoft.com/en-us/azure/storage/common/storage-sas-overview)). **Note:** You must provide either this or `data_url`. We recommend `data_url` over `data` for most cases.
        - `data` string — Base64-encoded contents of the file you want to upload. **Note:** You must provide either this or `data_url`. We recommend `data_url` over `data` for most cases.
  - `attachments` object[] — An array of the attachments you would like upload.
    - `name` string, required — File name of the file you want to upload. We recommend providing something human-readable with a valid file extension (like `Resume.pdf`), as this might be shown in your customer's system.
    - `content_type` string — Content/MIME type of the file (e.g., `application/pdf`). If you provide `data`, this is required. If you provide `data_url`, this is optional and we'll attempt to use the `Content-Type` header of the response. **Note:** Please validate that the content type you provide is actually meaningful (and not something generic like [`application/octet-stream`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/MIME_types#applicationoctet-stream)). Especially when using object storage (like AWS S3), it's easy to accidentally discard the content types of user-provided files, so make sure to explicitly persist them when processing uploads from your users (see guides for [AWS](https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingMetadata.html#SysMetadata), [Google Cloud](https://cloud.google.com/storage/docs/metadata#content-type), and [Azure](https://learn.microsoft.com/en-us/rest/api/storageservices/put-blob#request-headers-all-blob-types)).
    - `data_url` string, uri — URL to the file you want to upload that can be accessed without authentication headers. We will download the content immediately when receiving the request, so the URL can be short-lived. If you're using an object storage provider (like AWS S3), we strongly recommend providing a signed URL for secure access (see guides for [AWS](https://docs.aws.amazon.com/AmazonS3/latest/userguide/ShareObjectPreSignedURL.html), [Google Cloud](https://cloud.google.com/storage/docs/access-control/signed-urls), and [Azure](https://learn.microsoft.com/en-us/azure/storage/common/storage-sas-overview)). **Note:** You must provide either this or `data_url`. We recommend `data_url` over `data` for most cases.
    - `data` string — Base64-encoded contents of the file you want to upload. **Note:** You must provide either this or `data_url`. We recommend `data_url` over `data` for most cases.
    - `type` 'CV' | 'COVER_LETTER' | 'OTHER', required — Type of the attachment in the ATS. This may affect where the uploaded file will be shown in your customer's system.
  - `source` object — **(⚠️ Deprecated - Use [automatic source writing](/ats/features/application-attribution#automatic-attribution) instead)** Optional source information that will be attached to the candidate. If you're a job board or recruiting service, you can use this to make sure your customers can see which candidates came from you. This is deprecated because writing sources requires users to do some setup in most ATSs.
    - `name` string — Name of the source (e.g., `"Example Job Board"`).
    - `unified_key` string
    - `id` string
  - `sourced_by` object — Credit the recruiter or team member who sourced this candidate. While the `source` field tracks the channel/platform (e.g., "Awesome Jobboard"), the `sourced_by` field tracks the individual person responsible for finding the candidate.
    - `user_id` string, required — The Kombo ID or Remote ID of the User. Use the Kombo ID directly, or prefix the remote ID with "remote:" to reference the user by their ID in the remote system.
  - `gdpr_consent` object — Optional GDPR consent information required in some jurisdictions (like the Czech Republic or Slovakia).
    - `expires_at` string, date-time — Until when the candidate has granted the company they're applying to permission to process their personal data.
    - `given` boolean — Whether the candidate has given consent.
  - `remote_fields` object — Additional fields that we will pass through to specific ATS systems.
    - `successfactors` object — Fields specific to SAP SuccessFactors.
      - `Candidate` object — Fields that we will pass through to SuccessFactor's `Candidate` object.
      - `JobApplication` object — Fields that we will pass through to SuccessFactor's `JobApplication` object.
      - `copyJobApplicationAttachments` boolean — If set to true, we will copy custom attachments from the JobApplication to the Candidate.
      - `update_existing_candidate` boolean, nullable — When the candidate already exists, whether to update the Candidate with the remote fields found under the Candidate entity.
    - `personio` object — Fields specific to Personio.
      - `application` object — Fields that we will pass through to Personio's `application` object.
    - `talentsoft` object — Fields specific to TalentSoft.
      - `applicant` object — Fields that we will pass through to TalentSoft's `applicant` object.
      - `application` object — Fields that we will pass through to TalentSoft's `application` object.
    - `teamtailor` object
      - `candidate` object — Fields that we will pass through to Teamtailor's `Candidate` object.
      - `application` object
        - `attributes` object — Fields that we will pass through to Teamtailor's attributes section `Job application` object.
    - `greenhouse` object — Fields specific to Greenhouse.
      - `candidate` object — Fields that we will pass through to Greenhouse's `Candidate` object.
      - `application` object — Fields that we will pass through to Greenhouse's `Application` object.
      - `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 (OAuth-based connector).
      - `candidate` object — Additional fields passed through to Greenhouse V3's `POST /v3/candidates` request body.
      - `application` object — Additional fields passed through to Greenhouse V3's `POST /v3/applications` request body.
    - `lever` object — Fields specific to Lever.
      - `candidate` object — Fields that we will pass through to Lever's `Candidate` object. Note: make sure to submit the keys and values in the correct form data format.
    - `workable` object — Workable specific remote fields for ATS actions.
      - `candidate` object — Fields that we will pass through to Workable's `Candidate` object.
      - `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.
    - `workday` object — Fields specific to Workday. The remote fields schema follows the documentation at https://community.workday.com/sites/default/files/file-hosting/productionapi/Recruiting/v43.0/Put_Candidate.html. Only defined fields are supported, if you need additional field support please reach out to Kombo support.
      - `Candidate_Data` object
        - `Name_Detail_Data` object
          - `Middle_Name` string — The candidate's middle name
          - `Social_Suffix_Reference` object — The WID of the social suffix reference for the candidate
            - `Predefined_Name_Component_ID` string, required
        - `Language_Reference` object — Used to set the candidate's primary language
          - `WID` string, required
        - `Job_Application_Data` object
          - `Job_Applied_To_Data` object
            - `Global_Personal_Information_Data` object
              - …
          - `Resume_Data` object
            - `Education_Data` object[]
              - …
            - `Skill_Data` object[]
              - …
            - `Language_Data` object[]
              - …
            - `Experience_Data` object[]
              - …
        - `Contact_Data` object
          - `Location_Data` object
            - `Address_Line_1` string
            - `Address_Line_2` string
            - `Postal_Code` string
            - `Region_Subdivision_1` string
            - `Country_Region_Reference` object
              - …
            - `Country_City_Reference` object
              - …
        - `Worker_Reference` object — Reference to the Worker (employee) to link the candidate to. Provide either WID or Employee_ID.
          - `WID` string
          - `Employee_ID` string
      - `Override_Source_Reference_WID` string — Used to override the automatic source WID.
    - `zohorecruit` object — Fields specific to Zoho Recruit.
      - `candidate` object — Fields that we will pass through to Zoho Recruit's `Candidate` object.
    - `bullhorn` object — Fields specific to Bullhorn.
      - `candidate` object — Fields that we will pass through to Bullhorn's `Candidate` object.
      - `job_submission` object — Fields that we will pass through to Bullhorn's `JobSubmission` object.
      - `existing_candidate_remote_id` string — The remote ID of the Bullhorn `Candidate` the application should be filed on. When set, we skip Bullhorn's duplicate detection and use exactly this candidate, which lets you pick the right record when several candidates share an email address or phone number. The request fails if the candidate does not exist (or was deleted) in Bullhorn.
    - `smartrecruiters` object — Fields specific to SmartRecruiters.
      - `candidate_with_questions` object — **(⚠️ Deprecated - Use the `candidate` field instead.)** Fields that we will pass through to the SmartRecruiters's `Candidate` object when created with screening question answers. This API is used: https://developers.smartrecruiters.com/reference/createcandidate-1
      - `candidate_without_questions` object — **(⚠️ Deprecated - Use the `candidate` field instead.)** Fields that we will pass through to the SmartRecruiters's `Candidate` object when created with screening question answers. This API is used: https://developers.smartrecruiters.com/reference/candidatesaddtojob-1
      - `candidate` object — Fields that we will pass through to the SmartRecruiters's `Candidate` object. This API is used: https://developers.smartrecruiters.com/reference/createcandidate-1
      - `consent_decisions` object — The consent decisions for the candidate. SmartRecruiters supports two consent models: 'Single' (use the `SINGLE` key) and 'Separated' (use `SMART_RECRUIT`, `SMART_CRM`, `SMART_MESSAGE_SMS`, and/or `SMART_MESSAGE_WHATSAPP` keys). When this field is provided, it takes precedence over the `gdpr_consent` field for the `consentDecisions` property. See: https://developers.smartrecruiters.com/docs/partners-post-an-application
        - `SINGLE` boolean
        - `SMART_RECRUIT` boolean
        - `SMART_CRM` boolean
        - `SMART_MESSAGE_SMS` boolean
        - `SMART_MESSAGE_WHATSAPP` boolean
    - `talentadore` object — Fields specific to Talentadore.
      - `applications` object — Fields that we will pass through to the Talentadore's when creating applications.
    - `guidecom` object — Fields specific to GuideCom.
      - `candidate` object — Fields that we will pass through to GuideCom's `Candidate` object.
    - `dvinci` object — Fields specific to d.vinci.
      - `application` object — Fields that we will pass through to d.vinci's application object. This API is used: https://static.dvinci-easy.com/files/d.vinci%20application-apply-api.html#jobs__id__applyApi_post
      - `candidate` object — Fields that we will pass through to d.vinci's candidate/application payload as top-level fields (e.g., dateOfBirth).
    - `hrworks` object — Fields specific to GuideCom.
      - `jobApplication` object — Fields that we will pass through to HRWorks's `Job Application` object. This API is used: https://developers.hrworks.de/docs/hrworks-api-v2/53021f035f62d-post-job-applications
    - `jobylon` object — Fields specific to Jobylon.
      - `application` object — Fields that we will pass through to Jobylon's create application [endpoint](https://developer.jobylon.com/push-api-and-webhooks#-xL0v)'s request body.
        - `message` string — The `message` field of Jobylon's create application endpoint's request body.
    - `avature` object — Fields specific to Avature.
      - `workflow` object
        - `step` object
          - `id` integer, required — The ID of the workflow step to assign to the candidate.
    - `recruitee` object — Fields specific to Recruitee.
      - `candidate` object
        - `cover_letter_text` string — The cover letter text as a string. This will be visible on the main candidate page. Can be provided together with the `cover_letter` attachment, which will end up in a separate `file` section.
    - `rexx` object — Fields specific to Rexx.
      - `candidate` object — Fields that we will pass through to Rexx's application form fields.
    - `umantis` object — Fields specific to Abacus Umantis.
      - `person` object — Fields that we will pass through to Abacus Umantis's "Create a person" endpoint's `attributes` when creating a candidate.
    - `piloga` object — Fields specific to P&I Loga.
      - `candidate` object — Additional candidate fields for P&I Loga that will be mapped to the application form.
        - `street` string — The street address of the candidate.
        - `geburtsdatum` string, date-time — The birth date of the candidate, written into the "Geburtsdatum" field of the application form. Format: `YYYY-MM-DD`
    - `pinpoint` object — Fields specific to Pinpoint.
      - `candidate` object — Fields that we will pass through to Pinpoint's `Candidate` object.
    - `covetorest` object — Fields specific to Coveto REST.
      - `candidate` object — Additional candidate fields that will be passed to the Coveto candidate creation.
        - `mandant` number, double — The mandant field for the candidate in Coveto.
        - `status` integer — The numeric status ID to assign to the candidate on creation in Coveto. Refer to your Coveto `/bewerber-status` endpoint for available IDs.
        - `aktiv` 'Ja' | 'Nein' — Whether the candidate is created as active (`Ja`) or inactive (`Nein`) in Coveto. If omitted, Coveto applies its default (active).

## Response `200`

POST /ats/candidates Positive response

- PostAtsCandidatesPositiveResponse
  - `status` 'success', required
  - `data` 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.
    - `first_name` string, nullable, required — First name of the candidate.
    - `last_name` string, nullable, required — Last name of the candidate.
    - `company` string, nullable, required — The current company of the candidate.
    - `title` string, nullable, required — The current job title of the candidate.
    - `confidential` boolean, nullable, required — Whether the candidate’s profile is confidential in the ATS.
    - `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.
    - `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`.
    - `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`.
    - `social_media` object[], nullable — List of social media accounts of the candidate.
      - `link` string, nullable
      - `type` string, nullable
      - `username` string, nullable
    - `location` object, nullable — Location of the candidate.
      - `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 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.
    - `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.
    - `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.
    - `applications` 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.
      - `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_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.
      - `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.
        - `name` string, nullable, required — The application stage name. For example, "Initial Screening".
        - `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.
        - `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.
        - `name` string, nullable, required — Title of the job.
        - `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.
    - `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.
      - `name` string, nullable, required
      - `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.
  - `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/revisions/4700ff777f86/schema)