Troubleshooting

If requests fail, run zero doctor check-connector --env-name ASHBY_TOKEN or zero doctor check-connector --url https://api.ashbyhq.com/application.list --method POST

Ashby returns 401 when the key is missing and 403 when the key is wrong, deactivated, or lacks permission for the endpoint. A 403 response with missing_endpoint_permission means the key is valid but needs the relevant Ashby API permission.

Authentication

All requests require HTTP Basic Auth with the API key as the username and an empty password. With curl, pass the token as:

-u "$ASHBY_TOKEN:"

Ashby's API is RPC-style: endpoints are usually POST /resource.method, and request parameters go in JSON bodies. Include both JSON headers on API calls:

-H "Accept: application/json; version=1" -H "Content-Type: application/json"