Learn how to get the newest data back from Kombo.
data-changed
. This is sent to your system whenever data has changed inside Kombo. For example, after:
/candidates
endpoint to fetch both candidates and their applications.
Furthermore, after every successful fetch from us, store the timestamp of when the respective fetch started. Use this timestamp during your next fetch and pass it with your requests to the Kombo API as the updated_after
query parameter. Kombo will then only return the entries that changed since that timestamp.
Read more about this here.
Good to know: The updated_after
filter also considers changes in models that are returned by the endpoint as nested values. For example, the /candidates
endpoint will include every candidate that has had changes to their list of applications, even if the candidate profile itself did not change.
Endpoint | Models |
---|---|
Get applications | ats_applications ats_application_stages ats_candidates ats_interviews ats_jobs ats_join_candidates_tags ats_offers ats_tags |
Get candidates | ats_candidates ats_application_stages ats_applications ats_jobs ats_join_candidates_tags ats_join_jobs_application_stages ats_tags |
Get interviews | ats_interviews ats_applications ats_candidates ats_jobs ats_join_interviews_users ats_users |
Get jobs | ats_jobs ats_application_stages ats_job_postings ats_join_jobs_application_stages ats_join_jobs_screening_questions ats_join_jobs_users ats_screening_questions ats_users |
Get offers | ats_offers ats_applications ats_candidates ats_jobs |
Get rejection reasons | ats_rejection_reasons |
updated_after
query parameter. Then upsert the data returned by Kombo and merge it with your existing data copy.