Built by Metorial, the integration platform for agentic AI.
Gets the exact candidate by ID or by an unambiguous email/name search. Multiple matches require a refined search or an exact ID; visibility depends on API-key permissions.
Creates a new job in Ashby with a title, required location and department/team IDs, and an optional default interview plan. Use list_organization to discover the location and department. Returns the created job's ID and basic details.
Updates a job's details, status, or compensation. Supports changing the title, location, department, status, and compensation in a single call.
Creates, updates, cancels, or lists interview schedules in Ashby. Use this tool to coordinate interview scheduling for candidates in the hiring pipeline.
Updates a candidate's profile in Ashby. Supports changing name, email, phone, social links, adding tags, creating notes, and assigning to projects. Multiple operations can be performed in a single call.
Creates a new application for a candidate on a job in Ashby. An application represents a candidate's progression through the hiring pipeline for a specific job. Optionally specify an interview plan, starting stage, source, or credited user.
Lists applications with pagination or retrieves detailed information about a specific application. Applications represent a candidate's progress through the hiring pipeline for a particular job.
Discovers departments, locations, users, sources, archive reasons, tags, candidates, projects, custom fields, interview plans/stages/interviews and hiring roles needed by the existing tools. Returns one page where pagination is supported; user search requires an exact email.
Lists one native job page, reads an exact jobId, or performs bounded title search. Status-only filtering uses the list endpoint. Combined title/status filtering applies status to the bounded search results.
Sets a custom field value on an Ashby entity. Use the list organization tool with `resourceType` set to `custom_fields` to discover definitions and their supported object types. Offer fields use manage_offer forms; this endpoint does not support Offer.
Updates an existing application in Ashby. Supports multiple actions: change the interview stage (optionally with an archive reason), change the application source, transfer the application to a different job, and add or remove hiring team members. Multiple actions can be performed in a single call.
Reads/lists offers, submits native offer forms, starts a version in an existing prepared process, or force-approves the exact latest version. Process, form, application and version IDs are distinct; no approval or delivery is implied by form submission.
Creates a candidate with a full name and primary personal email/phone. Social links are set with a separate documented update; these operations are not atomic. Other legacy contact types are rejected before writes.
Prepares a downloadable candidate file, resume or offer document using its exact provider file handle. Requires candidatesRead. Ashby-generated demo files may not be downloadable.
Shows the connected API key title, creation time, endpoint permissions and observed API version. Requires apiKeysRead. It does not identify a human user or reveal the key.