What we read
| From the ATS | Becomes |
|---|---|
| The candidate's email | The candidate's email (an existing candidate with that email is reused) |
| The candidate's name | The candidate's name (the part of the email before @ when the ATS has none) |
| The job and stage of the event | Which linked interview to invite to |
| The ATS's candidate reference | Kept to write the results back to the right candidate |
The invitation's externalId is ats:<id>, so the API and webhooks show which invitations came from the ATS. The fields are fixed: there's no mapping to configure.
Invited once
- A candidate is invited to a linked interview once, however often the ATS sends the event or a webhook is replayed.
- Events for jobs or stages that aren't linked are answered and ignored.
- On an outage the invitation is retried with backoff: 7 more tries, from 1 minute up to 4 hours apart (about 8 hours in all). A refusal (no interview minutes left, the interview unpublished) fails it and shows in the log.
Write-back
When the results are ready and the connection's write-back switch is on, one note goes to the candidate in the ATS. It's plain text (paragraphs of HTML for Breezy HR, whose notes are rich text), in English:
AI interview results: Backend engineer screen Coverage score: 78/100 (for review, not a hiring decision). Explained the caching design clearly and covered most expectations; the failure-handling answer stayed general. Full results: https://app.testee.ai/c/co_acme/sessions/Qx7vT2mKpL9nWb4sYc1e
- The note is written once (Greenhouse and Workable are checked for it before a retry; on the others an outage mid-write can rarely leave it twice). When the ATS rate-limits us we wait at least as long as it asks; outages back off and retry.
- If the ATS refuses our key, the connection shows Reconnect needed and the note waits for the reconnect.
- If the key may read but not write notes, only that note fails (the log says so) and invitations keep going: give the key the write permission.
- A candidate deleted in the ATS fails only that note.
What we keep
- ATS candidate records for 365 days after they arrived, the activity log for 90 days.
- Erasing a candidate (dashboard or API) deletes their ATS record too; only a one-way hash is kept for 30 days, so a replayed webhook can't invite them again.
- Disconnecting deletes everything about that connection.