Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Ashby Hiring Process (BYOK) — connector documentation

  • MCP endpoint: https://byok-ashby-hiring-process.connectorbay.com/mcp
  • REST API: POST https://byok-ashby-hiring-process.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-ashby-hiring-process.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Ashby Hiring Process Ashby API key (hiringProcessMetadataRead and interviewsRead permissions), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-ashby-hiring-process.connectorbay.com/health · Tool schemas: https://byok-ashby-hiring-process.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-ashby-hiring-process · agent@connectorbay.com

What Ashby Hiring Process (BYOK) is for

Ashby Hiring Process (BYOK) lets an AI assistant read your own Ashby Hiring Process data through the Ashby Hiring Process API with a key you supply (Ashby API key (hiringProcessMetadataRead and interviewsRead permissions)). Read-only: 12 tools (list_archive_reasons, list_close_reasons, list_custom_fields, list_candidate_tags, list_source_tracking_links, list_survey_form_definitions, list_feedback_form_definitions, list_interview_plans, list_interview_stages, list_interview_stage_groups, list_interviewer_pools, list_communication_templates). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.ashbyhq.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Ashby Hiring Process. Ashby Hiring Process and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which archive reasons are configured in Ashby?"
  • "Which close reasons does Ashby have for jobs?"
  • "What custom fields are defined in Ashby?"
  • "What candidate tags exist in Ashby?"
  • "What source tracking links are set up in Ashby?"
  • "What survey forms are defined in Ashby?"

What it does

  • list_archive_reasons: List the reasons used when archiving a candidate application: text, type (rejected by candidate, by organization, other) and archived flag. Needs the hiringProcessMetadataRead permission.
  • list_close_reasons: List the reasons used when closing a job or opening: text and archived flag. Needs the hiringProcessMetadataRead permission.
  • list_custom_fields: List custom field definitions (title, object type, field type, required flag, private flag, selectable values). Definitions only, no values. Needs the hiringProcessMetadataRead permission.
  • list_candidate_tags: List candidate tags with id, title and archived flag. Needs the hiringProcessMetadataRead permission.
  • list_source_tracking_links: List custom source tracking links (code, link, source id, enabled flag), optionally for one source. Needs the hiringProcessMetadataRead permission.
  • list_survey_form_definitions: List survey form definitions (title, survey type such as EEOC, Diversity or CandidateExperience, archived flag and the form structure). Definitions only, no submissions. Needs the hiringProcessMetadataRead permission.
  • list_feedback_form_definitions: List interview feedback form definitions (title, default flag, archived flag and the form structure). Definitions only, no submitted feedback. Needs the hiringProcessMetadataRead permission.
  • list_interview_plans: List published interview plans with title, archived flag and dates. Needs the hiringProcessMetadataRead permission.
  • list_interview_stages: List the stages of one interview plan in order: title, type and position. Needs the interviewsRead permission.
  • list_interview_stage_groups: List the interview stage groups of the organization in order: title, order and stage type. Needs the interviewsRead permission.
  • list_interviewer_pools: List interviewer pools with title, archived flag and training path. Needs the hiringProcessMetadataRead permission.
  • list_communication_templates: List enabled email communication templates: id, title, dates and intended types. Template bodies are not returned. Needs the hiringProcessMetadataRead permission.

BYOK key

You bring your own Ashby Hiring Process Ashby API key (hiringProcessMetadataRead and interviewsRead permissions) (https://developers.ashbyhq.com/docs/authentication). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.ashbyhq.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Ashby Hiring Process API (api.ashbyhq.com) with a BYOK key; documentation: https://developers.ashbyhq.com/reference/archivereasonlist-1. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Ashby Hiring Process. Ashby Hiring Process and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Ashby Hiring Process account.

Built for: Worldwide. Languages: English.