Skip to content

Applicant tracking systems

Where ATS connectors stand today, what works instead, and how to make Test Candidates work alongside the system you already use.

Last updated 6 October 2026

Where ATS support stands

There are no working ATS connectors today. The integrations page lists several systems and every one of them is marked Coming soon. Nothing connects yet.

The applicant tracking systems section of the integrations page, listing several systems each marked coming soon.

We would rather say that plainly than have you discover it after you have planned a process around it. Connectors are planned, and which ones get built first depends partly on what people tell us they use. There is a link on that section to do exactly that, and it is read.

The routes that work today

Until there is a connector for your system, there are two routes.

  • The API and webhooks. If your ATS can call an API or receive a POST, or you have someone who can write a small piece of middleware, you can invite candidates and bring results back automatically. More on that below.

  • The assessment link in your ATS's own emails. No code at all. More on that below too.

  • Zapier or Make. No code. Most ATSs have a Zapier or Make app, so you can link the two in a few clicks. See Zapier and Make.

Inviting candidates from your ATS

With the API. When a candidate reaches the right stage in your ATS, your middleware calls the invitation endpoint with their email address and name. They get the same invitation email the app sends, and someone already invited is not invited twice. See the API reference.

With your assessment link. Almost every applicant tracking system lets you send a templated email at a stage. Paste your assessment link into that template and the assessment becomes part of the flow you already have:

  1. Copy the assessment's link from your assessments list.
  2. Add it to the stage email template in your ATS, with a sentence saying roughly how long the assessment takes.
  3. Move candidates to that stage as normal.

Candidates register themselves through the link and appear on your assessment. See share your assessment link.

Use one assessment per role, so the candidates in Test Candidates line up with the role in your ATS.

Getting results back

  • A webhook and the API. assessmentCompleted or testCompleted tells your middleware when a candidate has finished, and the API gives you their full record. See webhooks and the API reference.
  • Export a CSV and attach or import it. Fine for a role you run occasionally. See download and export results.

Scores only come through once a result is unlocked, on every route. Writing them onto a candidate record in your ATS is something your middleware does; we cannot push them there ourselves.

What you will miss without a connector

  • Setting up from inside your ATS. Without a connector, the link between the two systems is something you build or a template you maintain.
  • Automatic score write-back onto the candidate record, unless your own middleware does it.
  • Status sync. A decision recorded in Test Candidates does not move anyone in your ATS, and the other way round.

For most teams running a handful of roles, the link in a template plus an export is genuinely enough, and it is available today.

Telling us which system you use

Email support@testcandidates.com with the system and roughly how many roles a year you run through it.