Documentation

Connect Ashby

Ashby is one key and nothing else to paste: you create an API key, Voyse checks it, and Voyse then registers its own webhooks and creates the field it writes candidate intent scores into. Ten minutes, most of it in Ashby.

Before you start

You need an Ashby administrator to create the key — if you can't see API Keys in Ashby, you don't have the permission for it.

Create the key in Ashby

  1. In Ashby, go to Admin → Integrations → API Keys.
  2. Select + New and give the key a name you'll recognise later, such as Voyse.
  3. Grant these permissions:
    • Jobs — read. Your open roles and their job postings.
    • Candidates — read and write. Candidates apply through Voyse, and the summary of what someone asked is written to their profile.
    • Hiring process — read and write. This covers custom fields, which is where the candidate intent score goes.
    • API keys — write. This is what lets Voyse register its own webhooks rather than asking you to create five of them by hand.
  4. Save, then copy the key. Ashby shows it once.

Leaving out API keys write costs you the automatic webhook setup, and leaving out Hiring process costs you the intent score. Neither stops roles or applications moving.

Connect it in Voyse

  1. Select Integrations in the sidebar.
  2. Under Connect an ATS, choose Ashby.
  3. Paste the key into API key and select Connect.
  4. The pill by the provider's name reads Connected, and Sync status fills in once the first import finishes.

While it connects, Voyse registers five webhooks in your Ashby account — job posting published, updated and unpublished, and application submitted and updated — and creates a custom field to hold the candidate intent score. Both happen without you doing anything.

Webhooks

There is nothing for you to set up. The Webhooks section reads Configured automatically. Job posting and application events are received in real time.

If registration didn't complete — usually because the key lacks API keys write — the section offers Complete setup instead. Fix the permission in Ashby first, then select it.

What comes across

Jobs whose status in Ashby is Open, and the job postings attached to them. A role you haven't opened yet won't appear, however complete its posting is.

Capabilities lists what your key allows:

Feature What you need in Ashby
Job Sync, Application Submit, Webhook Events Essential, and granted with the permissions above
Candidate Notes Candidates read and write
Candidate intent score Hiring process read and write

Check capabilities re-tests them, which is worth doing after you change the key's permissions in Ashby.

If it didn't work

  • Invalid Ashby credentials when you connect — the key was mistyped, or it has been revoked in Ashby. Create a new one and paste it again.
  • Candidate notes shows Not granted — the key can't read candidates. Add the Candidates permission in Ashby and select Check capabilities.
  • Complete setup is still offered after you select it — the key doesn't have API keys write. Ashby will not let anything register webhooks without it.

Your roles landing here is what the Import your roles step on your home screen waits for. The rest of the page — sync status, the activity log, disconnecting — is covered in Connect your ATS.