Ashby integration

Enterprise

Move the candidate in Ashby. Kendor sends the screen.

When a candidate enters the Ashby stage you choose, Kendor sends their coding screen. Status, score, result, a review link and the decision are written back to the application as fields, with one note, so recruiters see where things stand without leaving Ashby.

Request access See pricing

SettingsIntegrations

Organization · Acme

Applicant tracking

Send Kendor screens from your ATS and see the results there.

AshbyMoving an application into a chosen stage invites the candidate, and their status, score and review link appear on the application.

Connected with the key ending kq2D, since 2026-09-14.

Check againDisconnect

Stages that send a screenWhen an application enters the stage, the candidate gets the screen by email. A rule for one job wins over one for any job.

Technical screen in Senior Backend Engineer → Senior Backend screenRemove
Coding exercise in any job → Backend fundamentalsRemove

Recent invites from AshbyWhat Kendor last wrote to each application. A failed write is retried for a day.

ada.okafor@example.comSenior Backend screen · Senior Backend EngineerCompleted
liam.chen@example.comSenior Backend screen · Senior Backend EngineerStarted
noah.berg@example.comBackend fundamentals · Platform EngineerNot written yet; retrying

Written to AshbyApplication fields · Ada Okafor

Kendor status: Completed
Kendor score: 92
Kendor result: Passed
Kendor review: https://kendor.io/organization/12/attempts/4821
Kendor decision: Advanced

Note on the candidate

Kendor: Senior Backend screen: Passed, score 92/100, took 74 min. Review: https://kendor.io/organization/12/attempts/4821

A stage you choose is the trigger.

Pick an Ashby job, one of its stages and a live Kendor screen. Recruiters keep working in Ashby; moving an application into that stage emails the candidate their screen.

A rule covers one job, or a stage name on any job
A rule for one job wins over one for any job
The invite lands on your Kendor roster, marked as sent from Ashby

Stages that send a screen

JobSenior Backend EngineerStageTechnical screenKendor screenSenior Backend screen

Add rule

CandidatesScreens & pipeline

Ada Okaforada.okafor@example.com Direct invite

Senior Backend screenAshbyInvitedUnassignedInvited

Signed webhooks. Duplicates ignored.

Ashby tells Kendor about stage changes through a webhook signed with a secret only your org and Ashby know. Kendor checks the signature on every request and rejects anything that doesn't match. If Ashby delivers the same change twice, the candidate still gets one invite.

Each org has its own webhook URL and secret, stored encrypted
A failed write to Ashby is retried for a day
No email address in Ashby? Kendor leaves a note instead of an invite

Webhook/api/integrations/ashby/webhook/7f3c…e41a

14:02:11 POST candidateStageChange

✓ Ashby-Signature sha256 verified · 200

org 12: Ashby application 8d2f41c7 invited a***@example.com

14:02:40 POST candidateStageChange

✓ Ashby-Signature sha256 verified · 200

! application 8d2f41c7 already linked for this stage · skipped

14:05:03 POST candidateStageChange

✗ Ashby-Signature mismatch · 401 Unauthorized

Set up with one API key.

Create an API key in Ashby and paste it into Kendor's integration settings. Where the key allows, Kendor registers the webhook and creates its five fields on the application, then shows a checklist of what's done. Anything the key can't do comes with the steps to finish it in Ashby.

Changed the key's permissions in Ashby? Check again
Replace the key any time; the webhook keeps working
Disconnecting removes the key and the rules; invites already sent stay valid

Applicant trackingOrganization · Acme

AshbyMoving an application into a chosen stage invites the candidate, and their status, score and review link appear on the application.

Connected with the key ending kq2D, since 2026-09-14.

Paste a new key to replace itSave

The key can read jobs and write results.
Ashby tells Kendor when an application changes stage.
Results go into the Kendor fields on each application.

Check againDisconnect

How it works

Ashby stays the system of record.

Connect with an API key
Kendor checks the key's permissions and sets up the webhook and its fields where the key allows.
Map a stage to a screen
For one job, or for a stage name on any job, choose which stage sends which screen.
Read results in Ashby
Fields update as the candidate starts, finishes, is graded and is decided, with one note once the grade is in.

Questions

Which plan includes Ashby?

Enterprise. Write to hello@kendor.io and we'll switch it on with you.

Does Kendor work with other ATSs?

Ashby is the only ATS integration today. Without one, you can attach screens to Kendor job postings or invite candidates directly. If you use another ATS, tell us — it shapes what we build next.

How much does Kendor write to Ashby?

Five fields on the application (status, score, result, a review link and the decision) and one note on the candidate once the screen is graded. Code, activity and reviewer notes stay in Kendor.

Do we still need Kendor's job board?

No. Keep your jobs and pipeline in Ashby; Kendor runs the screens and reports back. The careers page is there if you want it.

More of Kendor

All features

Run your next screen on Kendor. Read what the code says.

Kendor works with engineering teams in the EU, the UK and the US. Tell us what you're hiring for and we'll set up your organization with you.