Video Interview ATS Integration and What It Should Actually Do

A video interview ATS integration is a data connection that lets your applicant tracking system start an interview, follow its progress and receive the result against the right candidate record without anyone retyping it. The result means four things, which are status, scores, the recording link and the transcript.

Plenty of what gets sold under the name delivers two of those four. Here is how to tell what you are being offered before the contract rather than after it.

What are the six kinds of video interview ATS integration?

Integrations come in six shapes. They differ in who builds them, who fixes them at two in the morning, and what happens when either vendor changes something.

Native means something specific you can check. In a proper partner integration, adding an interview stage to a job lets the ATS list the available interviews, send candidate details to the interview tool, and receive back an instance ID, a status, a score and a link to the full result. Both sides document that contract.

Write back matters as much as the trigger. Results can arrive as a note, a structured feedback form, a file on the profile or a tag, so ask which one. A note is cheapest to build and least useful, because nobody can sort, filter or report on a note.

Large enterprise HR suites run their own partner approval programmes on their own timelines. If your shortlisted vendor is not already approved for the suite you use, the honest answer to whether they can integrate this quarter is no.

Which data fields matter every day?

Nine fields carry almost all the value. For each one, ask which direction it moves.

• Candidate record. Name, email, phone, CV and requisition, almost always sent from the ATS to the 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.
• Invite sent. Created by the interview tool, but the send event must show in the ATS, or recruiters chase people who were never invited.
• Completion event. Ideally a webhook. If the vendor only polls, ask how often, because every fifteen minutes is fine and overnight is not.
• Recording link. A link rather than a file. Check whether it expires and whether it respects ATS permissions.
• Transcript. Often the most useful item, and the one most often left out because it is bulky.
• Scores. A single number is close to useless. Scores per question or per skill, with the supporting quote, can actually be reviewed.
• Structured feedback. It belongs in the ATS scorecard rather than in free text.
• Advance or reject action. Deliberately last, for reasons covered below.

Two forgotten fields cause real pain. Without the requisition or job ID, results attach to a person but not to an application, and reporting falls apart. Without the source field, you cannot later prove which channel produced your hires.

Scores deserve the most care because they drive decisions. The 2022 review by Sackett and colleagues in the Journal of Applied Psychology put structured interviews at a corrected validity of .42 against .19 for unstructured ones, so the structure behind a score matters as much as the number itself. Carry the rubric and the evidence into the ATS along with it.

How do one way and two way sync differ in daily use?

With one way sync, the ATS pushes candidates out and nothing comes back automatically, or results come back while stage changes do not. With two way sync, both systems update each other and agree on which one owns each field.

Getting this wrong shows up in three ways. The first is duplicate records. A candidate applies with a personal email and then completes the interview using a college email from the invite. Matching runs on email, so you now have two records, and the recruiter is looking at the empty one. In campus hiring season this multiplies fast.

The second is stale status. The interview tool marks someone complete while the ATS still shows invited, and a recruiter sends a reminder to someone who finished four days ago. That almost always traces back to a missing completion webhook.

The third is two systems with two truths. Recruiters keep both tabs open and start trusting the interview tool because it is right. Within a quarter the ATS reports describe a pipeline that does not exist.

Decide field ownership and write it down. The ATS owns identity and pipeline stage. The interview tool owns interview state and its outputs. Neither one writes to the fields the other owns.

In what order should status triggers fire?

These events race each other, so the order matters more than people expect.

1. A recruiter moves the application to the interview stage in the ATS. The ATS is always the trigger.
2. A webhook fires and the interview tool creates the invite against the candidate ID and the requisition ID.
3. A confirmation writes back to the ATS so the recruiter can see the invite went out.
4. The candidate completes the interview and a completion event fires.
5. The outputs write first, meaning the recording link, transcript and scores.
6. Only then does the stage move to interview complete.

Keep steps five and six in that order. Flip them and recruiters open a candidate marked complete with an empty results panel, which teaches them to distrust the automation. Leave automatic rejection out of the sequence at first, and build a manual resync button, because a webhook will fail silently at some point.

Do you need single sign on and user provisioning?

With more than about thirty interviewers, yes. Single sign on lets interviewers use their existing work login. User provisioning, usually through SCIM, creates, updates and switches off accounts in the interview tool automatically when people join, move or leave.

The real reason to insist on provisioning is offboarding. Interview recordings are sensitive personal data, and an account still active for a manager who left months ago is a breach waiting to happen. Under the Digital Personal Data Protection Act, 2023, Section 8(5) makes the employer responsible for reasonable security safeguards, including over processing done by a data processor such as your interview vendor.

The stakes are concrete. The Press Information Bureau summary of the DPDP Rules, notified on 14 November 2025, says that failing to keep reasonable security safeguards can attract a penalty of up to Rs 250 crore. The ICO, the data protection regulator in the United Kingdom, also found in its 2024 audit of AI recruitment tools that some providers kept candidate data indefinitely. Ask how long recordings are kept and who can delete them, and read our guide to candidate data privacy in hiring for retention in more depth. Many vendors charge extra for single sign on and provisioning, so price them during evaluation rather than at renewal.

Which questions expose a thin integration?

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

• Which ATS interface are you using, by name? Vague answers here predict everything else.
• Is the completion event a webhook you push, or something we poll, and how often?
• Can you show a real customer record after an interview, with names hidden, and point to where the score sits?
• Does the transcript sync, or only a link back to your portal?
• What happens if we reject a candidate in the ATS while their interview is in progress?
• Do you match on email alone or on email plus requisition ID, and what happens on a collision?
• Who authenticates, and when do tokens expire? A hiring freeze can quietly let a connection lapse.
• What permissions do you need on our side, and can they be narrowed?
• How many customers are live on our ATS, and can we speak to one at our volume?
• When the ATS ships a breaking change, who fixes it and how fast?

A vendor with a real integration answers all ten in a short call. One with an embedded panel tends to change the subject to user experience.

What if your ATS has no native connector?

This is common and workable. Middleware is the quickest start, though polling triggers and job limits cap how far it scales. Building direct gives you control at a permanent maintenance cost, paid per connector. Check API quotas before planning any bulk resync, since some platforms meter calls by the day.

The fallback most teams settle on is simple. Send a webhook from the interview tool to a small receiver, write results into the ATS through its candidate update endpoint, and run a nightly reconciliation job that catches whatever the webhooks dropped. Keep a CSV export as the manual escape hatch, and insist on seeing the whole flow run in a sandbox with your own field names before you sign.

An integration you can describe field by field is real. One described only as connecting to everything is a promise to build it later, on your budget. For the wider buying decision, see how to choose a video interview platform.

Sources

1. Journal of Applied Psychology, Sackett, Zhang, Berry and Lievens, Revisiting meta analytic estimates of validity in personnel selection, 2022
2. Ministry of Electronics and Information Technology, The Digital Personal Data Protection Act, 2023
3. Press Information Bureau, Government of India, DPDP Rules, 2025 Notified, 2025
4. Information Commissioner Office (UK ICO), ICO intervention into AI recruitment tools leads to better data protection for job seekers, 2024