Yes for the mainstream systems, though each piece connects through a different mechanism and only some of those connections run in both directions. Job distribution uses either an XML feed the board crawls on a schedule or a posting API: Indeed refreshes crawled feeds four times a day at six hour intervals [6], and LinkedIn tells partners to pick one method rather than both because running both creates duplicate postings [8]. Interview scheduling reads and writes Google Calendar or Outlook 365, and self-scheduling in Greenhouse Recruiting is limited to stages containing a single interview [3]. Because a recruiting CRM and an ATS both store people, duplicate handling matters: a Greenhouse merge overwrites the candidate_id that API and HRIS integrations rely on, and cannot be undone [4]. Connections to assessment, background check, offer, and HRIS vendors are event driven, with the ATS posting a request and the vendor calling a webhook when a status changes [11][13].
\n","summary":"Every mainstream ATS connects to job boards, calendars, and downstream vendors, but each connection uses a different mechanism and fails differently. Job feeds refresh on the board's crawl schedule rather than instantly, scheduling accuracy depends on each interviewer connecting a calendar, and source attribution survives only if the tracking token survives the click path. Duplicate candidate records are the most common reason data stops reconciling.","publishedAt":"2026-07-21T20:47:04.008","verifiedAt":"2026-07-21T00:00:00","editorialStatus":"APPROVED","lastReviewedAt":"2026-07-21T00:00:00","nextReviewDueAt":"2026-10-21T00:00:00","templateVersion":"v2","aliases":["Does an ATS integrate with a recruiting CRM?","How does interview scheduling integrate with Google Calendar and Outlook?","How do ATS job board integrations work?","Indeed XML feed versus Indeed Apply for employers","How does LinkedIn integrate with an ATS?","What is LinkedIn Recruiter System Connect?","Hosted apply versus redirect apply flow","Why do duplicate candidate records happen in an ATS?","How does an ATS hand off data to an HRIS at hire?","What is a unified ATS API?","Why does candidate source attribution get lost?","What to ask an ATS vendor about integrations"],"confidenceScore":88,"confidenceLabel":"High","canonicalUrl":null},"contributor":{"id":"ec39deab-44fe-48d8-9029-fefe993ab85a","slug":"answer-stack","displayName":"AnswerStack","websiteUrl":null},"contributorOrganizationProfile":{"entityId":"ec39deab-44fe-48d8-9029-fefe993ab85a","legalName":null,"description":null,"websiteUrl":null,"imageUrl":null,"slogan":null,"subtitle":null,"facts":[],"coiNote":null,"foundingDate":null,"numberOfEmployeesText":null,"contactPoint":null,"address":null,"headquartersText":null,"organizationType":null},"contributorPerson":{"slug":"answerstack-editorial-team","displayName":"AnswerStack Editorial Team"},"sections":[{"id":"dc01d458-6bd8-4984-adc7-8ef8fd4185dc","sectionKey":"what_integration_means","sectionType":"markdown_section","heading":"What does an integrated recruiting stack actually connect?","introMarkdown":"Five separate connections sit behind that question, and each uses a different mechanism. Jobs travel outward to boards through either an XML feed the board crawls or a posting API the ATS calls [8]. Applications travel back inward, either from a form the ATS hosts or from a board posting to an endpoint your system exposes [7]. Interview scheduling reads and writes a work calendar, in practice Google Calendar or Outlook 365 [3]. Assessment, background check, and offer vendors exchange requests and results over an API, with webhooks carrying status changes back [11][13]. At hire, a subset of candidate data moves into an HRIS or onboarding platform and becomes employee data [12].\n\n### The ATS holds the system of record for hiring\n\nCandidate data lives in the ATS as a person record with one or more application records attached, and every other system writes into that structure or reads from it. The split matters because one person can apply to several jobs, so the person and the application carry separate histories. Merge's recruiting data model uses the same shape, exposing candidates, applications, and jobs as related objects [10].\n\n### What a marketplace listing does not tell you\n\nA logo on an integration marketplace confirms only that a connection exists. The better signal is which objects a partner may read and write, which SmartRecruiters publishes as separate Application, Assessment, Job Board, and Offer APIs [11].","introHtml":"Five separate connections sit behind that question, and each uses a different mechanism. Jobs travel outward to boards through either an XML feed the board crawls or a posting API the ATS calls [8]. Applications travel back inward, either from a form the ATS hosts or from a board posting to an endpoint your system exposes [7]. Interview scheduling reads and writes a work calendar, in practice Google Calendar or Outlook 365 [3]. Assessment, background check, and offer vendors exchange requests and results over an API, with webhooks carrying status changes back [11][13]. At hire, a subset of candidate data moves into an HRIS or onboarding platform and becomes employee data [12].
\nCandidate data lives in the ATS as a person record with one or more application records attached, and every other system writes into that structure or reads from it. The split matters because one person can apply to several jobs, so the person and the application carry separate histories. Merge's recruiting data model uses the same shape, exposing candidates, applications, and jobs as related objects [10].
\nA logo on an integration marketplace confirms only that a connection exists. The better signal is which objects a partner may read and write, which SmartRecruiters publishes as separate Application, Assessment, Job Board, and Offer APIs [11].
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":10},{"id":"1670955f-5486-4aa3-8c15-832cc62cadd9","sectionKey":"approach_table","sectionType":"table_section","heading":"How do the integration approaches compare?","introMarkdown":"Recruiting integrations are built five ways, and most stacks run several at once.","introHtml":"Recruiting integrations are built five ways, and most stacks run several at once.
\n","outroMarkdown":"No approach is inherently better. Native modules remove data movement but tie you to one roadmap, certified apps cover common paths cheaply, and middleware mostly suits software companies rather than employers.","outroHtml":"No approach is inherently better. Native modules remove data movement but tie you to one roadmap, certified apps cover common paths cheaply, and middleware mostly suits software companies rather than employers.
\n","contentJson":{"rows":[{"cells":["Native module inside the ATS","Scheduling, CRM, or offers sit in the same database, so no data moves","Teams wanting one vendor and one support path","Whether it matches a specialist tool's depth, such as interviewer pools [5]"]},{"cells":["Certified marketplace app","The partner builds it, the ATS reviews it, a customer turns it on with settings [13]","Background checks, assessments, other standard workflows","Whether certification covers writing status back or only ordering [13]"]},{"cells":["Open API and webhooks","Your developers call the ATS API and subscribe to events it emits [10][11]","Custom logic, internal tools, reporting warehouses","Rate limits, version support, and who maintains the code [10]"]},{"cells":["Unified API middleware","One normalized API in front of many ATS platforms [10]","Software teams shipping one integration to many customers","Which fields are normalized, and which need custom mapping [10]"]},{"cells":["Job feed or job posting API","XML the board crawls on a schedule, or a call to its posting API [6][8]","Publishing and expiring jobs across boards","Refresh interval, required fields, and whether both methods duplicate posts [6][8]"]}],"columns":["Approach","How it connects","Where it fits","What to check"]},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":20},{"id":"bc1c27c2-b499-48ec-ad80-fc79048dddb0","sectionKey":"ats_and_crm_records","sectionType":"markdown_section","heading":"Where does candidate data live when both an ATS and a recruiting CRM hold people?","introMarkdown":"Both systems store people, and that overlap causes most recruiting data problems. An ATS holds applicants, while a recruiting CRM holds people who have not applied: sourced prospects, event contacts, silver medalists, and anyone in a nurture campaign. The same human often exists in both, under two identifiers and two job titles.\n\n### Two architectures, two different problems\n\nWhere the CRM is a module of the same platform, the person record is shared and there is nothing to sync. Where the CRM is a separate product, the two systems have to agree on a match key, almost always email address. Greenhouse Recruiting flags a possible duplicate when a profile matches your organization's Duplicate tag settings, for example the same email address, phone number, LinkedIn profile URL, or name [4].\n\n### A merge is not a reversible cleanup step\n\nMerging combines the values from both records and logs conflicts in the candidate's activity feed, which sounds harmless until you read what it does to identifiers. Greenhouse documents that manually merging profiles overwrites the candidate_id used through its API and HRIS integrations, that the secondary profile's ID stops appearing in the app and in the API, and that candidates cannot be un-merged [4]. Any system holding the old identifier then points at a record that no longer resolves, so deduplicate before ordering a background check or pushing a hire onward.","introHtml":"Both systems store people, and that overlap causes most recruiting data problems. An ATS holds applicants, while a recruiting CRM holds people who have not applied: sourced prospects, event contacts, silver medalists, and anyone in a nurture campaign. The same human often exists in both, under two identifiers and two job titles.
\nWhere the CRM is a module of the same platform, the person record is shared and there is nothing to sync. Where the CRM is a separate product, the two systems have to agree on a match key, almost always email address. Greenhouse Recruiting flags a possible duplicate when a profile matches your organization's Duplicate tag settings, for example the same email address, phone number, LinkedIn profile URL, or name [4].
\nMerging combines the values from both records and logs conflicts in the candidate's activity feed, which sounds harmless until you read what it does to identifiers. Greenhouse documents that manually merging profiles overwrites the candidate_id used through its API and HRIS integrations, that the secondary profile's ID stops appearing in the app and in the API, and that candidates cannot be un-merged [4]. Any system holding the old identifier then points at a record that no longer resolves, so deduplicate before ordering a background check or pushing a hire onward.
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":30},{"id":"9890e346-5a7f-4a3c-8df5-bca508a573bf","sectionKey":"scheduling","sectionType":"markdown_section","heading":"How does interview scheduling integrate with calendars?","introMarkdown":"Scheduling integrations read free and busy data from a work calendar and write the interview event back, which is why Google Calendar and Outlook 365 are the connections that matter [3]. Each interviewer connects their own calendar, and that per person step is the first quiet failure point, because someone who never connected appears completely free.\n\n### Self-scheduling covers less ground than most buyers assume\n\nCandidate self-scheduling sends a link the candidate uses to book against interviewer availability, and Greenhouse notes that self-scheduled interviews work with Google Calendar and Outlook 365 and can attach a Google Meet, Zoom, or Microsoft Teams link automatically [3]. The limit is scope: the feature applies only to stages containing one interview, such as a hiring manager screen, so panels and multi-interview loops still go through standard scheduling [3].\n\n### Panels, interviewer load, and time zones\n\nPanel scheduling is a constraint problem rather than a calendar lookup, since the system has to find one window that satisfies several people and their limits. Ashby handles this with interviewer pools that pull people in dynamically, daily or weekly interviewer limits, multi-day scheduling for panels split across dates, and automatic generation of candidate schedules for complex loops [5].\n\n### Rescheduling is the workflow that fails most often\n\nA reschedule is a delete plus a create executed across at least three systems: the interview record in the ATS, a calendar event on every interviewer's calendar, and the video conference link. Any system that received the create but not the delete keeps a stale event, which is how a candidate joins a call with an interviewer who believes it was cancelled. Ashby's two way event syncing reduces that exposure by updating its record when the work calendar changes [5], and testing a reschedule during evaluation matters more than testing a first booking.","introHtml":"Scheduling integrations read free and busy data from a work calendar and write the interview event back, which is why Google Calendar and Outlook 365 are the connections that matter [3]. Each interviewer connects their own calendar, and that per person step is the first quiet failure point, because someone who never connected appears completely free.
\nCandidate self-scheduling sends a link the candidate uses to book against interviewer availability, and Greenhouse notes that self-scheduled interviews work with Google Calendar and Outlook 365 and can attach a Google Meet, Zoom, or Microsoft Teams link automatically [3]. The limit is scope: the feature applies only to stages containing one interview, such as a hiring manager screen, so panels and multi-interview loops still go through standard scheduling [3].
\nPanel scheduling is a constraint problem rather than a calendar lookup, since the system has to find one window that satisfies several people and their limits. Ashby handles this with interviewer pools that pull people in dynamically, daily or weekly interviewer limits, multi-day scheduling for panels split across dates, and automatic generation of candidate schedules for complex loops [5].
\nA reschedule is a delete plus a create executed across at least three systems: the interview record in the ATS, a calendar event on every interviewer's calendar, and the video conference link. Any system that received the create but not the delete keeps a stale event, which is how a candidate joins a call with an interviewer who believes it was cancelled. Ashby's two way event syncing reduces that exposure by updating its record when the work calendar changes [5], and testing a reschedule during evaluation matters more than testing a first booking.
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":40},{"id":"afaacd1a-e5bc-4bfb-8d59-0daf4e6a9057","sectionKey":"job_distribution","sectionType":"markdown_section","heading":"How do job boards, job distribution, and the apply flow actually connect?","introMarkdown":"Boards ingest jobs two ways, and you have to pick one. LinkedIn documents an XML feed that sends jobs when a customer creates them and a Job Posting API that posts them directly, with explicit guidance to use one or the other to avoid duplication [8]. It also separates free basic jobs, gathered from applicant tracking systems and aggregators, from paid promoted jobs posted through the API into purchased job slots [8].\n\n### Feeds refresh on the board's schedule, not yours\n\nIndeed's Job Sync XML feed defines your jobs and how they appear, and requires elements including title, an ISO-8601 date, a unique reference number, a requisition ID, the job URL, company, location, and a description matching the career site [6]. Indeed refreshes a crawled URL or FTP feed four times a day at six hour intervals, and an Indeed hosted FTP as often as every two hours when it receives a new file [6]. A requisition can stay visible for hours after it closes in the ATS.\n\n### Hosted apply and redirect are a real trade-off\n\nThe apply flow decides both completion rate and data quality. Greenhouse offers five careers page options, from a redirect to a Greenhouse hosted board, through an iframe embed and an API driven board with the application still hosted by Greenhouse, to a fully API driven build with the form on your own site [1]. Indeed Apply sits at the other end, keeping the candidate on Indeed and posting the application to a URL you specify in the feed as JSON carrying name fields, a Base64 encoded resume, screener answers, and analytics marking it organic, sponsored, or an Indeed Targeted Ad [7]. Indeed states that jobs using its Easily apply option receive 12% more clicks [7]. Fewer steps generally produce more completed applications, while a form you host collects custom questions a board profile does not carry, so compare completions per click rather than raw counts.","introHtml":"Boards ingest jobs two ways, and you have to pick one. LinkedIn documents an XML feed that sends jobs when a customer creates them and a Job Posting API that posts them directly, with explicit guidance to use one or the other to avoid duplication [8]. It also separates free basic jobs, gathered from applicant tracking systems and aggregators, from paid promoted jobs posted through the API into purchased job slots [8].
\nIndeed's Job Sync XML feed defines your jobs and how they appear, and requires elements including title, an ISO-8601 date, a unique reference number, a requisition ID, the job URL, company, location, and a description matching the career site [6]. Indeed refreshes a crawled URL or FTP feed four times a day at six hour intervals, and an Indeed hosted FTP as often as every two hours when it receives a new file [6]. A requisition can stay visible for hours after it closes in the ATS.
\nThe apply flow decides both completion rate and data quality. Greenhouse offers five careers page options, from a redirect to a Greenhouse hosted board, through an iframe embed and an API driven board with the application still hosted by Greenhouse, to a fully API driven build with the form on your own site [1]. Indeed Apply sits at the other end, keeping the candidate on Indeed and posting the application to a URL you specify in the feed as JSON carrying name fields, a Base64 encoded resume, screener answers, and analytics marking it organic, sponsored, or an Indeed Targeted Ad [7]. Indeed states that jobs using its Easily apply option receive 12% more clicks [7]. Fewer steps generally produce more completed applications, while a form you host collects custom questions a board profile does not carry, so compare completions per click rather than raw counts.
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":50},{"id":"8a3148dd-2b37-46ce-aa63-ffae511d3a7d","sectionKey":"downstream_handoffs","sectionType":"markdown_section","heading":"How do assessment, background check, offer, and HRIS connections work?","introMarkdown":"These connections share one pattern: the ATS sends a request, the vendor works asynchronously for minutes or days, and a webhook carries the result back. SmartRecruiters exposes to partners an Application API, an Assessment API for requests and results, a Job Board API in XML, an Offer API, and webhooks, reached through a partner API key or an OAuth flow [11].\n\n### Background checks carry compliance weight along with the data\n\nCheckr gives partners two ordering paths, and the difference is who touches candidate personal information. In the recommended hosted flow, the partner calls the invitations endpoint and Checkr emails the candidate to collect information and consent, creating the report once the invitation is completed [13]. In the self hosted flow, the partner collects the personal data directly and accepts more of the compliance responsibility [13]. This is not legal advice; United States background screening is governed by the Fair Credit Reporting Act plus state and local law, and software does not move that obligation off the employer.\n\n### The move into an HRIS at hire is a field mapping exercise\n\nHire is where recruiting data becomes employee data, and the field set is smaller than people expect. Workable exports to connected HRIS and onboarding platforms automatically when a candidate reaches the hired stage, moving photo, first and last name, personal email address, job title, start date, the resume as a PDF, LinkedIn URL, and user status [12]. Everything payroll and benefits need beyond that gets collected during onboarding. Write the field map down before go live, because a preferred name overwriting a legal name and a start date that changes after the export fired are the two failures that show up most often.","introHtml":"These connections share one pattern: the ATS sends a request, the vendor works asynchronously for minutes or days, and a webhook carries the result back. SmartRecruiters exposes to partners an Application API, an Assessment API for requests and results, a Job Board API in XML, an Offer API, and webhooks, reached through a partner API key or an OAuth flow [11].
\nCheckr gives partners two ordering paths, and the difference is who touches candidate personal information. In the recommended hosted flow, the partner calls the invitations endpoint and Checkr emails the candidate to collect information and consent, creating the report once the invitation is completed [13]. In the self hosted flow, the partner collects the personal data directly and accepts more of the compliance responsibility [13]. This is not legal advice; United States background screening is governed by the Fair Credit Reporting Act plus state and local law, and software does not move that obligation off the employer.
\nHire is where recruiting data becomes employee data, and the field set is smaller than people expect. Workable exports to connected HRIS and onboarding platforms automatically when a candidate reaches the hired stage, moving photo, first and last name, personal email address, job title, start date, the resume as a PDF, LinkedIn URL, and user status [12]. Everything payroll and benefits need beyond that gets collected during onboarding. Write the field map down before go live, because a preferred name overwriting a legal name and a start date that changes after the export fired are the two failures that show up most often.
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":60},{"id":"c6835c23-43b9-4f2e-a696-faed921a2084","sectionKey":"what_breaks","sectionType":"markdown_section","heading":"What actually breaks in a recruiting integration?","introMarkdown":"Integration failures in recruiting are rarely outages; they are quiet data problems that surface weeks later in a report nobody trusts.\n\n### Duplicate candidate records\n\nDuplicates appear whenever two systems can create a person, and the cleanup carries consequences: a Greenhouse merge overwrites the candidate_id used by API and HRIS integrations, removes the secondary ID from the app and the API, and cannot be undone [4].\n\n### Status that never writes back\n\nMany integrations push one direction only, so a rejection in the ATS never reaches the sourcing tool and a recruiter keeps working a candidate who is already out. LinkedIn's Recruiter System Connect closes that loop, and it shows what two way sync costs: partners must be approved by LinkedIn, sign an agreement, complete five development modules, and pass certification [9].\n\n### Scheduling collisions\n\nAvailability is only as accurate as the calendars actually connected [3], and pools with daily and weekly limits reduce collisions by making interviewer load visible to the scheduler [5].\n\n### Lost source attribution\n\nGreenhouse attributes a candidate's source using a tracking link built from the job post URL plus a source token appended as a query parameter such as gh_src [2]. When a board rewrites the destination URL, or the candidate searches the job title and arrives another way, the application lands with no source or the wrong one, and cost per hire by channel comes from that field.\n\n### Resume parsing that disagrees between systems\n\nThe same resume can produce different fields in the board, the ATS, and a screening tool, because each runs its own parser. Indeed states that it does not send every JSON field in every request, so a receiver has to treat missing fields as empty [7].","introHtml":"Integration failures in recruiting are rarely outages; they are quiet data problems that surface weeks later in a report nobody trusts.
\nDuplicates appear whenever two systems can create a person, and the cleanup carries consequences: a Greenhouse merge overwrites the candidate_id used by API and HRIS integrations, removes the secondary ID from the app and the API, and cannot be undone [4].
\nMany integrations push one direction only, so a rejection in the ATS never reaches the sourcing tool and a recruiter keeps working a candidate who is already out. LinkedIn's Recruiter System Connect closes that loop, and it shows what two way sync costs: partners must be approved by LinkedIn, sign an agreement, complete five development modules, and pass certification [9].
\nAvailability is only as accurate as the calendars actually connected [3], and pools with daily and weekly limits reduce collisions by making interviewer load visible to the scheduler [5].
\nGreenhouse attributes a candidate's source using a tracking link built from the job post URL plus a source token appended as a query parameter such as gh_src [2]. When a board rewrites the destination URL, or the candidate searches the job title and arrives another way, the application lands with no source or the wrong one, and cost per hire by channel comes from that field.
\nThe same resume can produce different fields in the board, the ATS, and a screening tool, because each runs its own parser. Indeed states that it does not send every JSON field in every request, so a receiver has to treat missing fields as empty [7].
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":70},{"id":"a96c0ae0-c4fe-476d-9b64-74e065fafc29","sectionKey":"vendor_questions","sectionType":"markdown_section","heading":"What should you ask a vendor before you sign?","introMarkdown":"Ask about mechanics rather than about the marketplace, because every marketplace looks complete from the outside.\n\n- Which direction does each integration move, and what event triggers it? A connection firing only at hire behaves very differently from one syncing on every status change.\n- Which objects and fields are included, and can you see the field map in writing, as Workable publishes for its hired stage export [12]?\n- Who built the integration and who supports it when it fails? A partner app, a middleware connector, and your own code have different escalation paths [11][13].\n- What are the API rate limits and versioning policy, and how much notice comes before an old version is retired [10]?\n- How does scheduling handle a reschedule and a cancellation across every calendar and video link involved [5], and does self-scheduling cover panels or only single interview stages [3]?\n- How is candidate source captured for each channel, and what happens when the tracking token is stripped [2]?\n- What is the duplicate matching rule, and can a merge be reversed [4]?\n- Where do integration errors appear, and does anyone get notified [13]?\n\nOne point applies to the whole category: no mandatory data standard governs recruiting integrations. HR Open Standards describes itself as the only independent, non-profit, volunteer led organization developing specifications for human resource data exchange [14], and adoption is partial, which is why unified API providers exist to normalize vendor differences [10].","introHtml":"Ask about mechanics rather than about the marketplace, because every marketplace looks complete from the outside.
\nOne point applies to the whole category: no mandatory data standard governs recruiting integrations. HR Open Standards describes itself as the only independent, non-profit, volunteer led organization developing specifications for human resource data exchange [14], and adoption is partial, which is why unified API providers exist to normalize vendor differences [10].
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":80},{"id":"89242fb7-66e3-42b7-a626-8fce09b18192","sectionKey":"contributor_perspective","sectionType":"markdown_section","heading":"How this answer was researched","introMarkdown":"This answer was assembled from vendor and platform documentation read directly on the dates shown rather than from summaries or comparison sites. Each behavior came from the primary source that owns it: Greenhouse support documentation for careers page options, tracking links, self-scheduling, and candidate merging; Ashby's product pages for panel scheduling and interviewer pools; Indeed and LinkedIn partner documentation for job ingestion and apply flows; SmartRecruiters, Workable, Checkr, and Merge documentation for partner and API models. No vendor reviewed, sponsored, or approved this record.\n\nIntegration behavior changes faster than most published guidance, and field lists, rate limits, refresh intervals, and partner program availability can all change without notice. Treat every figure here as accurate on the verification date and confirm it against current vendor documentation before you build. Corrections from recruiting operations practitioners and vendors are welcome.","introHtml":"This answer was assembled from vendor and platform documentation read directly on the dates shown rather than from summaries or comparison sites. Each behavior came from the primary source that owns it: Greenhouse support documentation for careers page options, tracking links, self-scheduling, and candidate merging; Ashby's product pages for panel scheduling and interviewer pools; Indeed and LinkedIn partner documentation for job ingestion and apply flows; SmartRecruiters, Workable, Checkr, and Merge documentation for partner and API models. No vendor reviewed, sponsored, or approved this record.
\nIntegration behavior changes faster than most published guidance, and field lists, rate limits, refresh intervals, and partner program availability can all change without notice. Treat every figure here as accurate on the verification date and confirm it against current vendor documentation before you build. Corrections from recruiting operations practitioners and vendors are welcome.
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":"This answer was written and reviewed by the AnswerStack Editorial Team, which has no commercial stake in the products, companies, or methods discussed. Every claim is cited inline and verified on the dates shown.","noteHtml":"This answer was written and reviewed by the AnswerStack Editorial Team, which has no commercial stake in the products, companies, or methods discussed. Every claim is cited inline and verified on the dates shown.
\n","sortOrder":90}],"citations":[{"title":"Choose a careers page integration option","url":"https://support.greenhouse.io/hc/en-us/articles/200721644-Choose-a-careers-page-integration-option","excerpt":"Make a quick and simple change to the code on your website that redirects to your job board on Greenhouse.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-21T00:00:00","supportsText":"the five careers page options spanning redirect to a Greenhouse hosted board, iframe embed, API driven board with hosted application, embedded board and form, and fully API driven board","domain":"support.greenhouse.io","publisherName":"Greenhouse Support"},{"title":"Tracking links overview","url":"https://support.greenhouse.io/hc/en-us/articles/216904366-Tracking-links-overview","excerpt":"A source token is a combination of numbers and letters at the end of your URL that uniquely identifies the source.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-21T00:00:00","supportsText":"source attribution mechanics: a tracking link is the job post URL plus a source token appended as a query parameter such as gh_src","domain":"support.greenhouse.io","publisherName":"Greenhouse Support"},{"title":"Candidate self-scheduling overview","url":"https://support.greenhouse.io/hc/en-us/articles/4409534663579-Candidate-self-scheduling-overview","excerpt":"Self-scheduled interviews can be integrated with Google Calendar and Outlook 365.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-21T00:00:00","supportsText":"self-scheduling supports Google Calendar and Outlook 365, attaches Google Meet, Zoom, or Microsoft Teams links, allows a single date and time based on interviewer availability, and applies only to stages with a single interview","domain":"support.greenhouse.io","publisherName":"Greenhouse Support"},{"title":"Merge duplicate candidate profiles","url":"https://support.greenhouse.io/hc/en-us/articles/115004506466-Merge-duplicate-candidate-profiles","excerpt":"Manually merging candidate profiles will overwrite the candidate_id field used to identify candidates when utilizing our API or HRIS integrations in Greenhouse Recruiting.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-21T00:00:00","supportsText":"duplicate detection by email, phone, LinkedIn URL, or name; merging overwrites the candidate_id used by API and HRIS integrations; the secondary ID disappears from app and API; merges cannot be undone","domain":"support.greenhouse.io","publisherName":"Greenhouse Support"},{"title":"Scheduling features","url":"https://www.ashbyhq.com/platform/recruiting/scheduling","excerpt":"Group interviewers into pools and dynamically pull them in during the scheduling process.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-21T00:00:00","supportsText":"interviewer pools, interviewer preferences and daily or weekly limits, multi-day scheduling, automatic generation of multiple schedules for panels and loops, two-way event syncing, and a scheduling view spanning interviewers, candidate availability, and time zones","domain":"ashbyhq.com","publisherName":"Ashby"},{"title":"Job Sync XML feed reference","url":"https://docs.indeed.com/indeed-apply/xml-feed","excerpt":"For XML that Indeed crawls on a URL or hosts on an FTP server you provide, Indeed refreshes the job data four times a day at six-hour intervals, starting from the time of the last request.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-21T00:00:00","supportsText":"required XML feed elements including title, ISO-8601 date, referencenumber, requisitionid, url, company, location fields, email, and description; refresh four times a day at six hour intervals, and as often as every two hours for Indeed hosted FTP","domain":"docs.indeed.com","publisherName":"Indeed Partner Docs"},{"title":"Direct employer integration with Indeed Apply","url":"https://docs.indeed.com/indeed-apply/direct-employer","excerpt":"To process applications programmatically, specify a URL that accepts POST requests from Indeed Apply.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-21T00:00:00","supportsText":"applications delivered as JSON POST to a postUrl, Base64 encoded resume files in txt, pdf, doc, docx, or rtf, screener answers, organic versus sponsored versus Indeed Targeted Ad analytics, the HTTP 2XX acknowledgment requirement, missing JSON fields, and the 12% more clicks figure for Easily apply","domain":"docs.indeed.com","publisherName":"Indeed Partner Docs"},{"title":"Job Posting Overview","url":"https://learn.microsoft.com/en-us/linkedin/talent/job-postings/job-posting-overview","excerpt":"To avoid duplication, use either of the above solutions to ingest jobs on LinkedIn.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-21T00:00:00","supportsText":"two ingestion methods (Job Posting API and XML feeds), the instruction to use one or the other to avoid duplication, and the split between free basic jobs and paid promoted jobs including job slots","domain":"learn.microsoft.com","publisherName":"LinkedIn Talent Solutions (Microsoft Learn)"},{"title":"Recruiter System Connect Overview","url":"https://learn.microsoft.com/en-us/linkedin/talent/recruiter-system-connect","excerpt":"Recruiter System Connect synchronizes customers' candidate information between your ATS and LinkedIn Recruiter.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-21T00:00:00","supportsText":"two-way candidate synchronization between an ATS and LinkedIn Recruiter, syncing candidates, applications, and notes so the in-ATS indicator is accurate, plus partner approval, API agreement, five development modules, and certification","domain":"learn.microsoft.com","publisherName":"LinkedIn Talent Solutions (Microsoft Learn)"},{"title":"Recruiting (ATS) Unified API overview","url":"https://docs.merge.dev/merge-unified/ats/overview","excerpt":"Launch: 100 / minute (per Linked Account), Professional: 400 / minute, Enterprise: 600 / minute.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-21T00:00:00","supportsText":"unified API model with normalized common models for candidates, applications, and jobs, field expansion into related objects, the recommendation to combine webhooks with polling using modified_after, and per minute rate limits of 100, 400, and 600 by plan tier","domain":"docs.merge.dev","publisherName":"Merge"},{"title":"Partners overview","url":"https://developers.smartrecruiters.com/docs/partners-overview","excerpt":"The Marketplace API provides access to the Application API, Assessment API, Job Board API, Offer API, and Webhooks.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-21T00:00:00","supportsText":"partner APIs exposed to marketplace partners including Application, Assessment, Job Board (XML), and Offer APIs, webhooks for event driven integration, and partner API key plus OAuth authorization flows","domain":"developers.smartrecruiters.com","publisherName":"SmartRecruiters Developer Documentation"},{"title":"HRIS and onboarding integration for partners","url":"https://www.workable.com/developers/partner-program/hris-onboarding","excerpt":"After connecting, data exports happen automatically when candidates reach the hired stage.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-21T00:00:00","supportsText":"automatic export at the hired stage and the specific fields transferred: photo or avatar, first and last name, personal email, job title, start date, resume PDF, LinkedIn URL, and user status","domain":"workable.com","publisherName":"Workable"},{"title":"Checkr Partner Developer Guides","url":"https://docs.checkr.com/partners/","excerpt":"Checkr sends an invitation email to the candidate to provide their information and consent, and once the invitation is completed a Report is automatically created.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-21T00:00:00","supportsText":"OAuth account connection, the hosted invitation flow versus the self hosted reports flow, webhook retry schedule of every minute for ten minutes then every hour for 24 hours, and the required integration review before production","domain":"docs.checkr.com","publisherName":"Checkr"},{"title":"HR Open Standards","url":"https://www.hropenstandards.org/","excerpt":"the only independent, non-profit, volunteer-led organization dedicated to the development and promotion of a standard suite of specifications to enable human resource related data exchanges","quoteText":null,"sourceRole":"INDEPENDENT","verifiedAt":"2026-07-21T00:00:00","supportsText":"the absence of a single mandatory recruiting data standard and the existence of voluntary consensus specifications for HR data exchange","domain":"hropenstandards.org","publisherName":"HR Open Standards Consortium"}],"revisions":[],"relatedAnswers":[{"id":"16031afa-f1b4-48f0-a1d5-02aee75c7ab0","slug":"applicant-tracking-system-worth-it-or-can-i-hire","question":"Is an applicant tracking system worth it, or can I hire without one?","publishedAt":"2026-07-21T20:47:06.493","confidenceScore":88,"confidenceLabel":"High","industry":{"id":"e1a1da3c-52a8-4e99-88ad-d08ef17d7c3f","slug":"hr-technology","label":"HR Technology","description":"ATS, HRIS, payroll, and workforce management"},"topic":{"slug":"recruiting-applicant-tracking","label":"Recruiting & Applicant Tracking","description":"ATS, Recruiting CRM, Recruitment Marketing & Sourcing, Resume Parsing, Interview Scheduling, Video Interviewing","schemaKind":null},"contributor":{"id":"ec39deab-44fe-48d8-9029-fefe993ab85a","slug":"answer-stack","displayName":"AnswerStack","websiteUrl":null},"snippet":"Manual hiring out of an inbox and a spreadsheet is viable for roughly one to five openings a year with a single decision maker. It gets expensive once applicant counts climb, several interviewers need the same view, or you have to reproduce dated hiring records.","url":"/q/applicant-tracking-system-worth-it-or-can-i-hire"},{"id":"3bac1883-0c14-4b6f-976c-fd911d262bb6","slug":"whats-the-best-video-interviewing-software-and-are-one-way","question":"What's the best video interviewing software, and are one-way (asynchronous) interviews actually effective?","publishedAt":"2026-07-21T20:47:01.388","confidenceScore":82,"confidenceLabel":"High","industry":{"id":"e1a1da3c-52a8-4e99-88ad-d08ef17d7c3f","slug":"hr-technology","label":"HR Technology","description":"ATS, HRIS, payroll, and workforce management"},"topic":{"slug":"recruiting-applicant-tracking","label":"Recruiting & Applicant Tracking","description":"ATS, Recruiting CRM, Recruitment Marketing & Sourcing, Resume Parsing, Interview Scheduling, Video Interviewing","schemaKind":null},"contributor":{"id":"ec39deab-44fe-48d8-9029-fefe993ab85a","slug":"answer-stack","displayName":"AnswerStack","websiteUrl":null},"snippet":"Video interviewing splits into live interviewing with scorecards, one-way asynchronous platforms, and interview recording tools. Spark Hire and Willo publish prices; HireVue, VidCruiter and Jobma publish none. One-way interviews reliably cut scheduling work, but the validity evidence supports interview structure rather than the video format. Automated scoring adds Illinois, New York City and Colorado notice, consent and audit duties.","url":"/q/whats-the-best-video-interviewing-software-and-are-one-way"},{"id":"6a0b325a-7e5b-422e-b774-fbe3507ee1d5","slug":"whats-the-best-candidate-sourcing-and-recruitment-marketing-software","question":"What's the best candidate sourcing and recruitment marketing software, and does AI sourcing actually work?","publishedAt":"2026-07-21T20:46:58.551","confidenceScore":82,"confidenceLabel":"High","industry":{"id":"e1a1da3c-52a8-4e99-88ad-d08ef17d7c3f","slug":"hr-technology","label":"HR Technology","description":"ATS, HRIS, payroll, and workforce management"},"topic":{"slug":"recruiting-applicant-tracking","label":"Recruiting & Applicant Tracking","description":"ATS, Recruiting CRM, Recruitment Marketing & Sourcing, Resume Parsing, Interview Scheduling, Video Interviewing","schemaKind":null},"contributor":{"id":"ec39deab-44fe-48d8-9029-fefe993ab85a","slug":"answer-stack","displayName":"AnswerStack","websiteUrl":null},"snippet":"Sourcing software and recruitment marketing software are different categories. Sourcing tools find and contact passive candidates; recruitment marketing tools build a pipeline through career sites, talent CRM, and job distribution. Published prices run from roughly $99 a month for a solo seat to quote-only enterprise contracts. AI helps most with search and outreach drafting, least with predicting job performance, and automated ranking carries bias risk plus compliance duties in New York City, Illinois, and Colorado.","url":"/q/whats-the-best-candidate-sourcing-and-recruitment-marketing-software"},{"id":"32043e52-e7bf-4cf9-be88-8a47da8f1889","slug":"applicant-tracking-systems-automatically-reject-or-filter-out-resumes","question":"Do applicant tracking systems automatically reject or filter out resumes before a human sees them?","publishedAt":"2026-07-21T20:46:55.96","confidenceScore":86,"confidenceLabel":"High","industry":{"id":"e1a1da3c-52a8-4e99-88ad-d08ef17d7c3f","slug":"hr-technology","label":"HR Technology","description":"ATS, HRIS, payroll, and workforce management"},"topic":{"slug":"recruiting-applicant-tracking","label":"Recruiting & Applicant Tracking","description":"ATS, Recruiting CRM, Recruitment Marketing & Sourcing, Resume Parsing, Interview Scheduling, Video Interviewing","schemaKind":null},"contributor":{"id":"ec39deab-44fe-48d8-9029-fefe993ab85a","slug":"answer-stack","displayName":"AnswerStack","websiteUrl":null},"snippet":"An applicant tracking system is mainly a database and workflow tool. It can auto-reject on knockout questions the employer configured, and parsing errors or ranking can quietly push an application down the queue, but blanket automatic rejection is not how most systems work. The 75 percent auto-rejection figure has no traceable source. Recruiter capacity explains most silence: applications per job rose 111 percent from 2022 to 2025 while recruiting teams shrank by more than half.","url":"/q/applicant-tracking-systems-automatically-reject-or-filter-out-resumes"}],"contributorStats":{"verifiedAnswers":224,"openDisputes":0},"schemaJson":{"@context":"https://schema.org","@type":"Question","name":"Does the recruiting stack integrate: ATS, CRM, interview scheduling, and job boards?","text":"Does the recruiting stack integrate: ATS, CRM, interview scheduling, and job boards?","url":"https://www.answerstack.io/q/recruiting-stack-integrate-ats-crm-interview-scheduling-and-job","answerCount":1,"datePublished":"2026-07-21T20:47:04.008","author":{"@type":"Person","name":"AnswerStack Editorial Team","worksFor":{"@type":"Organization","name":"AnswerStack"},"url":"https://www.answerstack.io/contributors/answer-stack"},"about":[{"@type":"Thing","name":"Recruiting & Applicant Tracking"},{"@type":"Thing","name":"HR Technology"}],"acceptedAnswer":{"@type":"Answer","text":"Yes for the mainstream systems, though each piece connects through a different mechanism and only some of those connections run in both directions. Job distribution uses either an XML feed the board crawls on a schedule or a posting API: Indeed refreshes crawled feeds four times a day at six hour intervals [6], and LinkedIn tells partners to pick one method rather than both because running both creates duplicate postings [8]. Interview scheduling reads and writes Google Calendar or Outlook 365, and self-scheduling in Greenhouse Recruiting is limited to stages containing a single interview [3]. Because a recruiting CRM and an ATS both store people, duplicate handling matters: a Greenhouse merge overwrites the candidate_id that API and HRIS integrations rely on, and cannot be undone [4]. Connections to assessment, background check, offer, and HRIS vendors are event driven, with the ATS posting a request and the vendor calling a webhook when a status changes [11][13].","url":"https://www.answerstack.io/q/recruiting-stack-integrate-ats-crm-interview-scheduling-and-job","upvoteCount":0,"datePublished":"2026-07-21T20:47:04.008","dateModified":"2026-07-21T00:00:00","author":{"@type":"Person","name":"AnswerStack Editorial Team","worksFor":{"@type":"Organization","name":"AnswerStack"},"url":"https://www.answerstack.io/contributors/answer-stack"},"citation":[{"@type":"CreativeWork","name":"Choose a careers page integration option","url":"https://support.greenhouse.io/hc/en-us/articles/200721644-Choose-a-careers-page-integration-option"},{"@type":"CreativeWork","name":"Tracking links overview","url":"https://support.greenhouse.io/hc/en-us/articles/216904366-Tracking-links-overview"},{"@type":"CreativeWork","name":"Candidate self-scheduling overview","url":"https://support.greenhouse.io/hc/en-us/articles/4409534663579-Candidate-self-scheduling-overview"},{"@type":"CreativeWork","name":"Merge duplicate candidate profiles","url":"https://support.greenhouse.io/hc/en-us/articles/115004506466-Merge-duplicate-candidate-profiles"},{"@type":"CreativeWork","name":"Scheduling features","url":"https://www.ashbyhq.com/platform/recruiting/scheduling"},{"@type":"CreativeWork","name":"Job Sync XML feed reference","url":"https://docs.indeed.com/indeed-apply/xml-feed"},{"@type":"CreativeWork","name":"Direct employer integration with Indeed Apply","url":"https://docs.indeed.com/indeed-apply/direct-employer"},{"@type":"CreativeWork","name":"Job Posting Overview","url":"https://learn.microsoft.com/en-us/linkedin/talent/job-postings/job-posting-overview"},{"@type":"CreativeWork","name":"Recruiter System Connect Overview","url":"https://learn.microsoft.com/en-us/linkedin/talent/recruiter-system-connect"},{"@type":"CreativeWork","name":"Recruiting (ATS) Unified API overview","url":"https://docs.merge.dev/merge-unified/ats/overview"},{"@type":"CreativeWork","name":"Partners overview","url":"https://developers.smartrecruiters.com/docs/partners-overview"},{"@type":"CreativeWork","name":"HRIS and onboarding integration for partners","url":"https://www.workable.com/developers/partner-program/hris-onboarding"},{"@type":"CreativeWork","name":"Checkr Partner Developer Guides","url":"https://docs.checkr.com/partners/"},{"@type":"CreativeWork","name":"HR Open Standards","url":"https://www.hropenstandards.org/"}]}}}