Video Interview ATS Integration: What "We Integrate With Everything" Actually Means

The Greenhouse partner directory lists 520 integrations. Almost every video interview vendor claims one of those slots, and they don't all mean the same thing by the word. A video interview ATS integration is a data connection that lets your applicant tracking system trigger an interview, follow its progress, and receive the result — status, score, recording link, transcript — against the correct candidate record, without a human retyping anything. That is the whole definition. Plenty of what gets sold under the name delivers two of those four things and calls it done.

Here's how to tell which one you're being offered, before the contract rather than after.

What are the six types of video interview ATS integration?

Recruitment software integrations fall into six shapes, and they are not variations on a theme. They differ in who builds them, who fixes them at 2am, and what happens when the vendor ships a breaking change.

Native means something specific and checkable. Greenhouse's Assessment API defines the shape precisely: the partner exposes four endpoints, and when a partner assessment stage is added to a job's hiring plan, Greenhouse calls list_tests to show the available interviews, calls send_test with the candidate's name, email, phone and resume URL, then either polls test_status or waits for the partner to PATCH a completion. The partner returns a test instance ID, a status, a numeric score and a link back to the full result. That is a real integration with a documented contract on both sides.

Lever does the same job differently. An assessment partner subscribes to the candidateStageChange webhook, fires the interview when the opportunity hits the configured stage, and writes results back as a note, a feedback form, a PDF on the profile, or a tag — each needing its own OAuth scope, such as feedback:write:admin or files:write:admin. Ask a vendor which of those four they use. "Notes" is the cheapest to build and the least useful, because a note doesn't sort, filter or report.

Workday is a different animal. You cannot simply decide to integrate with it. HireVue's integration page says it uses Workday's APIs directly with no middleware, and it carries the Workday Certified badge; HackerRank and Paradox announced the same certification, for assessments and scheduling, distributed through Workday Marketplace. Certification is Workday's programme, on Workday's timeline. If your shortlisted vendor is not already certified, the honest answer to "can you integrate with Workday" is "not this quarter".

Getting listed at all is a filter. Greenhouse's partner programme requires at least one mutual customer and a live privacy policy before you apply, reviews submissions on the first Monday of each month, and states plainly that not all are accepted.

Which data fields actually matter in a recruitment integration?

Nine fields carry almost all of the value. Ask which direction each one moves.

• Candidate record — name, email, phone, resume, requisition. Almost always ATS to interview tool. The matching key is usually email, which is where duplicates begin.
• Stage or status — the trigger and the receipt. This is the field most often one-way when it needs to be two-way.
• Interview invite — created by the interview tool, but the send event must be visible in the ATS, or recruiters chase candidates who were never invited.
• Completion event — a webhook, ideally. If the vendor only supports polling, ask the interval. Fifteen minutes is fine. Overnight is not.
• Recording link — a URL, not a file. Check whether it expires, and whether it honours ATS permissions or is open to anyone holding it.
• Transcript — increasingly the most useful artifact, and the one most often left out of the sync because it is bulky.
• Score — a single number is nearly useless. Per-question scores with the supporting quote are reviewable.
• Interviewer notes and structured feedback — should land in the ATS scorecard object, not as free text in a note.
• Rejection or advance action — deliberately last. See below.

Two forgotten fields cause real pain: the requisition or job ID (without it, results attach to a candidate but not an application, and reporting collapses), and the source field, which is how you later prove which channel produced hires.

What's the difference between one-way and two-way sync, and why does it matter daily?

One-way sync means the ATS pushes candidates out and nothing comes back automatically, or results come back but stage changes don't. Two-way means both systems update each other and agree on which one owns each field.

Getting it wrong has three consequences, and every recruiting ops person has lived at least one.

Duplicate records. A candidate applies with a personal Gmail address, then completes the video interview using the college address on the invite. Matching is on email. You now have two records, one with an interview result and one without, and the recruiter is looking at the empty one. In campus hiring seasons — the September and January placement waves that dominate Indian volume recruitment — this compounds fast.

Stale statuses. The interview tool marks a candidate complete. The ATS still shows "invited". A recruiter sends a chaser to someone who finished four days ago. This is the single most common complaint about thin ATS integration with interview software, and it comes from a missing completion webhook.

Two systems, two truths. Recruiters keep both tabs open and start trusting the interview tool, because the interview tool is right. Within a quarter your ATS reporting is fiction and the hiring manager dashboard gets quietly abandoned.

Decide field ownership and write it down. The ATS owns candidate identity and pipeline stage. The interview tool owns interview state and artifacts. Neither writes to the other's fields. That rule prevents most sync wars.

How should status-change triggers be sequenced?

Order matters more than people expect. These events race.

1. Recruiter moves the application to the video interview stage in the ATS. The ATS is the trigger, always — never the interview tool.
2. Webhook fires. Interview tool creates the invite against the candidate ID and the requisition ID.
3. Invite sent. A confirmation event writes back to the ATS so the recruiter can see it left.
4. Candidate completes. Completion event fires.
5. Artifacts write first — recording link, transcript, per-question scores land on the application.
6. Only then does the stage advance to "interview complete".

Steps 5 and 6 in that order, not the reverse. Flip them and recruiters click into a candidate marked complete with an empty results panel, which trains them to stop trusting the automation. Keep auto-rejection out of the sequence entirely, at least at first. And build a manual re-sync button; you will need it the first time a webhook delivery fails silently.

Do you need SSO and user provisioning?

If you have more than about thirty interviewers, yes. SAML single sign-on means interviewers use their existing corporate login. SCIM provisioning means that when someone joins, moves team or leaves, their account in the interview tool is created, updated or deactivated automatically from your identity provider.

The reason to insist on SCIM is offboarding, not convenience. It is the least glamorous part of HR system integration for recruitment and the part auditors ask about first, because video interview recordings are sensitive candidate data. Under India's Digital Personal Data Protection Act, 2023, whose rules were notified on 14 November 2025 with an eighteen-month phased compliance window, and under the EU AI Act's Article 50 transparency duty that applied from 2 August 2026, you need to know who can see candidate material and be able to revoke it. An orphaned account belonging to a manager who left in March is a finding waiting to happen. Many vendors charge extra for SAML and SCIM, or gate them behind an enterprise tier. Price that in during evaluation, not renewal.

What questions expose a thin integration?

A thin video interview ATS integration survives a sales demo and dies in week three. Ask these on the technical call, with an engineer present, and get the answers in writing.

1. Which ATS API are you using — Harvest, the Assessment API, the Partner API? Name it. Vague answers here predict everything else.
2. Is the completion event a webhook you push, or something we poll? If polling, at what interval?
3. Show me a real customer's ATS record post-interview. Screenshot, not a mock. Where exactly does the score sit — a note, a custom field, or the native scorecard object?
4. Does the transcript sync, or only a link to your portal?
5. What happens when a candidate is rejected in the ATS while their interview is in progress?
6. How do you match candidates — email only, or email plus requisition ID? What happens on a collision?
7. Who authenticates: an admin API key or OAuth? If OAuth, what is the refresh token lifetime? Lever's refresh tokens expire after one year, or after 90 days of inactivity — a hiring freeze can silently kill the connection.
8. What API permissions do you need on our side? Greenhouse scopes keys by endpoint, but access to data within a permitted endpoint is all-or-nothing, which your security team will want to hear about before they find out.
9. How many customers are live on this specific ATS, and can we speak to one who runs our volume?
10. When the ATS ships a breaking change, who fixes it, and what is your committed turnaround?

A vendor with a real integration answers all ten in under ten minutes. One with an iframe will pivot to talking about user experience.

What if your ATS has no native connector?

This is the common case for teams on Zoho Recruit, Keka, Darwinbox or an in-house system, and it's workable. Every route below will connect video interviews to ATS records; they differ in how much work is yours and how fresh the data stays.

Start with middleware, but know its ceiling. Zapier's Greenhouse connector, for example, uses polling triggers such as New Candidate Application and New Scheduled Interview, requires a paid Zapier plan, and Zapier's own documentation warns it works for up to 100 jobs before performance suffers. Unified API providers like Merge sit one level up, offering a single interface across many ATS platforms; one Merge customer describes internal integrations as taking two to three sprints each, versus the same effort once for the whole set.

If you build direct, budget honestly. WorkOS estimates a single OAuth integration at roughly 150 hours of senior engineering to build, 300 hours a year to maintain, and about $48,000 in first-year cost including support load. Per connector.

Watch platform quotas before you plan a resync. Zoho Recruit meters API use in credits — 5,000 a day on Standard, 10,000 base on Professional — and a single bulk write initialisation costs 500 of them. Darwinbox's ATS API supports bulk candidate fetch, tagging and rejection over basic auth: enough for nightly reconciliation, not for real-time status.

The pragmatic fallback that most teams land on: webhook out from the interview tool into a small receiver, write results into the ATS through its create/update candidate endpoints, and run a nightly reconciliation job that catches whatever the webhooks dropped. Add a CSV export as the manual escape hatch. It's unglamorous and it works.

Whichever route you take, insist on seeing the integration running against a sandbox with your own field names before signing. Some platforms — Xakal's Xara AI Interviews among them — document the exact payload of the completion event up front, which is the level of specificity worth demanding from anyone you evaluate, at thexakal.com or elsewhere.

A video interview ATS integration you can describe field by field is real. One described only as "we connect to everything" is a promise to build it later, on your budget.