connect aperture with ashby
ashby stays your system of record. aperture attaches to a stage you already have, evaluates everyone who reaches it, and writes the result back onto the candidate.
you will need admin access on both sides, enough to create an api key in ashby and edit an interview plan. budget about fifteen minutes, most of it waiting for the sync.
set this up with an ai assistant
open integrations in aperture
in aperture, go to settings → integrations and pick ashby.
integrations
connect the system your pipeline already lives in. aperture reads the pipeline and writes its results back.
Ashby
two-way api key and webhook
Greenhouse
oauth service account
Lever
oauth
Workday
enterprise, on request
swap credentials in both directions
ashby uses a two-way exchange. aperture generates a key for you to paste into ashby, and waits for ashby's own key in return.
credentials
aperture api key
paste into ashbyapt_live_7f3c····························9e21ashby api key
paste into apertureashby_····························webhook url
paste into ashbyhttps://api.aperturehq.ai/v1/ashby/eventsgenerate ashby's key under admin → integrations → api keys → + new, then add the webhook url in ashby so stage changes reach aperture immediately.
a connection with only one half configured looks connected and moves no data. this is the most common setup mistake.
wait for the sync
aperture pulls your workspace across so both sides agree on the same state. wait for it to finish before configuring anything.
initial sync
departments and teams
12team members
516open jobs
38interview plans
38candidates in flight
1,204add aperture to an interview plan
open the job in ashby, go to its interview plan, pick a stage, and add an activity. this decides which candidates aperture evaluates.
interview plan
application review
recruiter screen
technical quiz
aperture
hiring manager
onsite
offer
the dropdown reads "Aperture AI Interview" because that is how ashby registers an assessment activity. what runs is the full suite: fraud detection, identity verification, λ-CORE scoring, and background verification.
move a candidate in
your normal workflow from here:
- move the candidate into the configured stage
- pick the session language when aperture prompts
- aperture sends the candidate their link directly
- ashby flips them to an interviewing state
read the results
ashby gets the headline, a λ-CORE score and pool rank on the candidate. aperture holds the full report: evaluated skills, strengths and weaknesses, session metadata, and the transcript.
candidate pool
tabitha
scored · λ-core
leopold
scored · λ-core
april
scored · λ-core
april scored 82 throughout. she moved from rank 1 to 3 because two stronger candidates joined. the score is fixed, the rank is a comparison.
a single scored candidate shows a score and no rank. that is expected. ranking is pool-relative, and a pool of one has nothing to compare against. how ranking works.
if something looks wrong
- nothing syncs: one half of the credential exchange is missing.
- a job is missing: the sync had not finished. re-check, then re-run it.
- no link sent: confirm the stage has the aperture activity and the webhook is registered in ashby.
- score but no rank: only one candidate scored so far.
building the ashby integration yourself? share this with your developers
the assessment partner api reference: the assessment.start webhook that triggers everything, what aperture does automatically once it fires, and the scopes the api key needs.
read the technical docscommon questions
how long does the ashby integration take to set up?
do i need to move my pipeline out of ashby?
why does the ashby dropdown say Aperture AI Interview?
why does a candidate have a score but no rank?
what permissions does aperture need in ashby?
ashby documentation
the official pages for the steps above. where they disagree with this guide, trust them. they are the source of truth for ashby's own screens.
- aperture: ashby integration referenceour own technical docs for this integration, including the assessment.start webhook
- how do i generate an api key?the admin → integrations → api keys path, and the permission checkboxes
- integrations overviewhow ashby handles third-party integrations generally
- api authenticationhow the api key is used on each request
- creating an assessments integrationthe assessment activity model behind the interview-plan step
- ashby knowledge baseeverything else
that is the whole setup
every candidate who reaches that stage in ashby is now evaluated automatically, and the score and pool rank come back to the candidate record your recruiters already work from. nothing else changes about how your team runs the pipeline.
stuck on a step?
email [email protected] with your workspace and the step you are on, and we will walk through it with you.
keep reading
related from aperture.
hiring
hiring is broken. the numbers say how badly.
the structural failure nobody is fixing
hiring
your best applicants never even reach you
the case for moving beyond keyword filters
candidates
can an ai interview discriminate against you?
a careful answer about fairness, what gets evaluated, and what gets ignored
from the product