Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: Basic auth.
  • Connection: HTTP Basic auth with ASHBY_API_KEY as the username and ASHBY_API_PASSWORD as the password.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration.

​
Setup

  1. Sign in to Ashby: Go to https://app.ashbyhq.com and sign in as an organization admin. Ashby is a paid product - use your company workspace or request a sandbox from Ashby support.
  2. Create an API key: Open Admin → API → API Keys and create a key. Grant read permissions for Candidates, Jobs, and Applications (plus candidate write if you will use Create Candidate).
  3. Set environment variables: Add ASHBY_API_KEY=<your key> to your .env. Leave ASHBY_API_PASSWORD unset or empty - Ashby uses the key as the Basic auth username with a blank password.
  4. Verify access: Run List Jobs to confirm the key works.

​
Provider notes

  • All Ashby endpoints are POST-based RPC calls (e.g. candidate.list) with JSON bodies; list/info/search calls do not modify data
  • Authentication is HTTP Basic with the API key as username and an empty password
  • Responses are wrapped as {success, results, moreDataAvailable, nextCursor}; tools unwrap ‘results’
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as ashby__list_candidates with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.