Bullhorn API and MCP server

Bullhorn gives API keys only to contracted technology vendors, not to the agency that wants its own agent to match candidates, add notes or submit. Sign in to Bullhorn once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Not affiliated with Bullhorn.

Bullhorn's own API leaves this out. So we run one for you.

Bullhorn's own API, a GitHub MCP server and Cotlet compared
What you need Bullhorn's APIGitHub MCP serverCotlet
Notes, submissions, matches, statuses No No Yes, 9 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when Bullhorn changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 23, 2026. Sources: Bullhorn: API access FAQs · Bullhorn Help: Managing Notes in Bullhorn ATS · Bullhorn Help: Submitting a Candidate to a Job · Bullhorn Developer Guide: Creating a Submission

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to Bullhorn in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect Bullhorn to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 9 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. Bullhorn and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    Claude Code
    claude mcp add --transport http cotlet \
      https://cotlet.dev/mcp/v1 \
      --header "Authorization: Bearer $COTLET_API_KEY"
    Cursor
    {
      "mcpServers": {
        "cotlet": {
          "url": "https://cotlet.dev/mcp/v1",
          "headers": {
            "Authorization": "Bearer ${COTLET_API_KEY}"
          }
        }
      }
    }
    Codex
    # ~/.codex/config.toml
    [mcp_servers.cotlet]
    url = "https://cotlet.dev/mcp/v1"
    bearer_token_env_var = "COTLET_API_KEY"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/bullhorn with its own method and path, such as POST /api/v1/bullhorn/jobs/{job_id}/submissions, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the Bullhorn API and MCP server do?

9 tools on your own Bullhorn account. Agents call them as operations of the MCP tools bullhorn_read and bullhorn_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

Bullhorn tools in Cotlet's MCP server and REST API
Tool What it does Access
search_candidates Candidates matching keywords in name, occupation, company, resume, work history and attachments. read
get_candidate One candidate record with status, current company and the jobs they were submitted to. read
list_candidate_notes Notes on a candidate's Notes tab with Note Action, author and date, newest first. read
get_job One job record with title, client, owner, location and submission count. read
find_matching_candidates Candidates that match a job by its description and location, like Find Matching Candidates. read
list_job_submissions Submissions on a job by stage, with candidate, status and date. read
add_note Adds a note with a Note Action to a candidate's Notes tab. writeasks first
add_submission Submits one or more candidates to a job for the job owner to review. writeasks first
update_submission_status Moves one submission to another status in your hiring workflow. writeasks first

Scroll the table for all 9 tools.

Ask in plain words. Your agent does the rest.

Is it safe to connect Bullhorn?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

How much do the Bullhorn API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Each call uses 10 credits, and your Cloud Browser uses 50 credits a day while Bullhorn is enabled for agents, so 20 calls a day come to 250 credits.

Cotlet credit packs: price, credits and calls at 10 credits each
Credits Price, one time Calls at 10 credits Per 1,000 credits
5,000 $29 500 $5.80
15,000 $79 1,500 $5.27
32,000 $149 3,200 $4.66
60,000 $249 6,000 $4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.

Questions

Does Bullhorn have an API?

Bullhorn has a REST API, but it is sold as a paid partner contract to technology vendors, not as a key for a recruiter or an agency (checked 23 Oct 2026). Bullhorn does not allow middleware or connector companies to build on it and has no official MCP server.

How do I get access?

Sign up free, open Bullhorn under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 9 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Bullhorn yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Bullhorn sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: add_note, add_submission, update_submission_status wait for your OK by default. You can switch that off per tool for scheduled runs.

Can my agency get a Bullhorn API key for its own agent?

Bullhorn sells API access as a partner contract to technology vendors, with an upfront annual fee and a security assessment. Bullhorn also says customers do not get their key if they plan to hand it to a vendor without a contract. Cotlet does not use that API: your agent works in your own Bullhorn login in the Cloud Browser.

Which Bullhorn role do I need?

Your own user, with the rights it already has. Your agent can only open records and do actions that your user can do in Bullhorn. Changing the status of a candidate that is not yours needs the Change Any Candidate Submission Status entitlement, and a call without it fails.

Should I use a Bullhorn MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when Bullhorn changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

Who runs Cotlet?

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

Is Cotlet affiliated with Bullhorn?

No. Cotlet is independent and not affiliated with Bullhorn.

Give your agent access to Bullhorn.

Free 7-day trial with 2,000 credits, no card needed.