Connecting JobCannon to Ashby
Setup guide for JobCannon on Ashby: the single-field API key, the three endpoints, why assessments are ordered from the interview plan, and the www-host 401 trap.
JobCannon is an Ashby partner assessment provider. The adapter is built; it is enabled per organisation on request rather than self-serve, so start by emailing partners@jobcannon.io.
Quick reference
| Property | Value |
|---|---|
| Auth method | HTTP Basic, one API key that JobCannon issues |
| Base URL | https://jobcannon.io/api/integrations/ashby |
| Endpoints | assessment.list, assessment.start, assessment.cancel |
| Result delivery | JobCannon POSTs to https://api.ashbyhq.com/assessment.update |
callback_url | Not used — Ashby does not hand one out |
| Availability | Enabled per organisation on request |
🔴 Use the apex host. Measured against a real credential: https://jobcannon.io/api/integrations/ashby authenticates, https://www.jobcannon.io/api/integrations/ashby returns 401 Missing credentials. Cloudflare answers the www host with a 308 to the apex, and a client drops Authorization across an origin-changing redirect — so the apex genuinely receives no credentials and correctly says so. Before you conclude your key is wrong, re-run it against the apex.
Step 1: Ask us to enable it
Email partners@jobcannon.io with your Ashby workspace name and the admin address for credentials. We issue one API key.
Step 2: Enter the key in Ashby
Ashby's admin panel has a single field for a partner credential. Paste the key exactly as issued. JobCannon accepts the key in any Basic Auth position Ashby might place it — key:, :key, user:key, or a bare key with no colon — because Ashby's documentation does not specify which, and guessing wrong produces a 401 indistinguishable from a bad key. All four work.
Base URL: https://jobcannon.io/api/integrations/ashby.
Step 3: Attach an assessment to an interview plan
This is where the Ashby model differs from Greenhouse, and it catches people out.
There is no per-candidate "order an assessment" call you make. In Ashby, an admin picks a JobCannon assessment while configuring a job's interview plan. Ashby calls assessment.list at the moment that dropdown opens — that is the first request JobCannon ever sees from your workspace, and seeing it is how you know the credential works. When a candidate reaches that part of the plan, the Ashby user starts the assessment and Ashby calls assessment.start.
So: configure the interview plan first. If you are testing and no request arrives, the plan is the thing to check, not the credential.
Step 4: Verify
- Open a job's interview plan and the assessment dropdown. JobCannon assessments should be listed — that is
assessment.listanswering. - Add one to a stage and save.
- Move a test candidate (using an address you control) to that stage and start the assessment.
- Complete it from the emailed link.
- JobCannon scores it and pushes the result to Ashby with
assessment.update.
Result push runs on an hourly flush, so allow up to an hour.
Cancelling
assessment.cancel withdraws an ordered assessment. A cancelled session reads back as cancelled and the candidate's link stops working.
Common errors
**401 Missing credentials** — the www host, nine times out of ten. See the note above. Otherwise the key was rotated or deactivated.
Assessment dropdown is empty in Ashby — the credential authenticated but the org has no catalogue access, or you are on a workspace we have not enabled. Tell us the workspace name.
Nothing happens when a candidate reaches the stage — Ashby prompts the recruiter to start the assessment; it does not fire automatically. Someone has to click.
Verification checklist
- ☐Key entered in Ashby, apex host
- ☐
assessment.listobserved (assessments appear in the interview-plan dropdown) - ☐An assessment attached to a stage on a real job
- ☐A test candidate started and completed one
- ☐The result appeared on the candidate in Ashby
Vendor docs: https://developers.ashbyhq.com/reference Support: partners@jobcannon.io