Hashlogics
Answers

Bullhorn, Avionte and Greenhouse APIs: what a real integration involves

Each system lets a custom tool in through credentials your agency controls, and each draws the line on writes in a different place.

Answered in short

5 things that decide this

  1. 01Integrating with Bullhorn, Avionte or Greenhouse means Bullhorn's OAuth and REST session, Avionte's developer portal and certification route, and Greenhouse's Harvest API under the agency's keys. Hashlogics builds screening and onboarding tools on all three.
  2. 02Bullhorn's REST API runs on OAuth 2.0. You swap the access token for a BhRestToken session key, which every later call carries, against an entity model of candidates, job orders and placements.
  3. 03Avionte publishes a developer portal for its BOLD front-office and back-office APIs. Your own developers start there, while outside vendors go through Avionte's Certified Integration Program.
  4. 04Greenhouse's Harvest API v3 uses OAuth 2.0 credentials that a Greenhouse admin creates and scopes. Harvest v1 and v2 were removed on August 31, 2026, so older integrations need moving.
  5. 05Building a tool for your own agency is a different track from listing a product on the Bullhorn Marketplace or certifying with Avionte, and most agency builds only need the first.
Bullhorn

Bullhorn: an entity model that matches how a desk works

Bullhorn's entity model doesn't ask you to translate your workflow into vendor terms. The names are already what your recruiters think in: a Candidate, a JobOrder, a Placement, a ClientContact at the firm that opened the req. Agents built on it feel native to your team once the link itself works.

Your connection starts with OAuth 2.0. An access token comes back through the normal login flow, and you swap it for a BhRestToken, the session key every later call carries. It's a two-step handshake, so a build that assumes step one's token works everywhere will break.

The two access tracks

Your own instance versus a Bullhorn Marketplace integration

Two questions hide under "Bullhorn API access", and they have different answers. A custom tool for your own desks needs only API keys and the entity model above. A Bullhorn Marketplace integration is a separate track. It's a product other agencies can install, and Bullhorn's own review decides what gets listed.

Most of what your agency needs is the first kind: screening agents, resurfacing, compliance gates, redeployment check-ins. It's built for your instance and tested against your data, so it never needs a marketplace review. We confirm which track applies against Bullhorn's current programme terms during the audit.

Avionte

Avionte: a developer portal and a certification route

Avionte publishes its API documentation at developer.avionte.com. Its BOLD Front Office API lets you reach talent, companies, contacts, jobs, placements and pipelines. Back Office APIs cover payroll, billing, invoices and timesheets, and webhooks report front-office and back-office events as they happen.

Access starts with credentials issued for your Avionte account, then an access token from Avionte's authorization API. Your own developers can build against it as an Avionte customer. A vendor selling to many agencies goes through Avionte's Certified Integration Program instead. That's a business review as well as a tech one.

Some endpoints are partner-only. Avionte's docs say some talent benefit calls fail unless the caller is a benefit partner. Check the ones you need before you plan around them.

Greenhouse

Greenhouse: the Harvest API and scoped credentials

If you run Greenhouse, in-house work runs on its Harvest API. Your Greenhouse admin creates the credentials in the Dev Center and picks which endpoints each one can reach. Within an endpoint, Greenhouse says access is all or nothing, so you scope by endpoint, not by field.

Harvest v3 uses OAuth 2.0. A tool for your own account uses the client credentials flow, and a partner product uses the authorization code flow. Harvest v1 and v2 were removed on August 31, 2026, so a tool still sending a basic API key needs moving to v3.

It writes as well as reads. It can create candidates and applications, add notes and attachments, update candidate details, and advance, move or reject applications. That last power is why your build needs a rule about who decides a rejection.

Side by side

The access route, system by system

From each vendor's own developer docs on the date shown. Your plan, your modules and the permissions your admin grants decide what a build can actually touch.

SystemHow a custom tool gets inWho holds the keysTypical writes
BullhornOAuth 2.0, then a BhRestToken sessionYour agency's Bullhorn adminNotes, tasks, appointments, candidate fields
AvionteDeveloper portal and an access token; vendors certifyYour agency, via its Avionte accountTalent, jobs and placements through BOLD
GreenhouseHarvest API v3, OAuth 2.0 with endpoint scopesA Greenhouse admin in the Dev CenterCandidates, applications, notes, stage moves
What a build for a desk actually doesLive
  1. Resume or intake arrivesParsed and matched against the Candidate entity
  2. Screening passRanked shortlist with reasons; recruiter decides
  3. SchedulingWritten as a Task or Appointment on the record
  4. ResurfacingExisting candidates matched when a new JobOrder lands
  5. Redeployment check-inA note logged on the Placement as a contractor's assignment ends

Every one of these writes into Bullhorn objects a recruiter already works in.

What people actually build

Screening, resurfacing, redeployment and compliance gates

Screening and scheduling agents are what you're likely to want first, in any of the three systems. They run a first pass on new candidates against a job's needs and write a ranked shortlist with reasons back as a note. Then a recruiter makes the real call, so the decision stays human.

Resurfacing tends to matter more than you'd expect going in. Your Bullhorn base piles up years of records, and most never get pulled back up. Nobody's search finds a fair match twice. An agent that scans your pool on each new job finds people you already own, not people you have to find again.

Compliance gates and redeployment check-ins both write to the Placement record as the source of truth. Your gate blocks dispatch until right-to-work or a credential is confirmed. A check-in logs a note as a contractor's assignment winds down. Your desk sees a warm bench, not a candidate who's gone quiet.

  • 01Screening agents that rank candidates against a JobOrder and write reasons a recruiter can check, along with a score.
  • 02Resurfacing that re-reads the Candidate pool on every new JobOrder, instead of leaving it to a fresh Boolean search.
  • 03Compliance gates on the Placement record that block dispatch until the check clears, logged rather than reported after the fact.
Proof

What we have shipped for regulated staffing

We built Shift Link, an AI workforce compliance and scheduling platform for a UK recruitment firm that supplies temporary staff to healthcare, logistics and warehousing. Workers upload documents in the app, and the UK Right-to-Work API checks them and stores the expiry date. Compliance status then decides which shifts each worker can take, just as your placements would.

Shift Link cut manual compliance verification by 70%. Your build would use the same pattern. An outside check writes its result to the record your desk already uses, before a placement goes ahead.

Who to hire

Who builds Bullhorn, Avionte and Greenhouse integrations

Hashlogics scopes a Bullhorn, Avionte or Greenhouse integration from the access your agency can grant today. For Bullhorn, that's OAuth keys your agency asks Bullhorn support for, then the BhRestToken session. Avionte means credentials for your own account on its developer hub. Greenhouse means Harvest v3 credentials that a Site Admin creates in the Dev Center and scopes by endpoint. No outside firm has any of these until your agency says yes.

Once access is confirmed, a fixed-fee Blueprint turns it into a written spec, credited in full against the build. That spec names the Candidate, JobOrder and Placement fields the tool reads. It names what it writes back, such as a note or a task. It also names who signs off before an application moves stage or gets rejected. If the plan isn't one you'd act on, you don't pay for it.

Delivery runs as fixed-price milestones. You accept each one against written criteria, like a shortlist that lands on the JobOrder with a reason beside every name. Your agency owns the code and the keys. Our wider staffing work sits on the staffing agency hub.

Questions, answered
01Which development firms integrate custom tools with Bullhorn, Avionte or Greenhouse?+

Hashlogics builds screening, onboarding and compliance tools on Bullhorn, Avionte and Greenhouse, using credentials your agency controls. We built Shift Link, a staffing compliance platform that checks right-to-work before a worker can take a shift. Every project starts by confirming what your account exposes.

02Can a small agency get Bullhorn API access without going through Marketplace?+

Yes. A custom build for your own agency's instance is a separate, simpler track from a Bullhorn Marketplace integration meant for other agencies to install. Most single-agency projects never touch the Marketplace review.

03Does Avionte have an open API?+

Avionte publishes its API documentation openly at developer.avionte.com and calls it an open API programme for customers' own developers. Live access still needs credentials for your account. Vendors building for many agencies go through Avionte's Certified Integration Program.

04What can the Greenhouse Harvest API write?+

Harvest can create candidates and applications, add notes and attachments, update candidate details, and advance, move or reject applications. Each credential only reaches the endpoints your Greenhouse admin grants it. Access inside an endpoint is all or nothing.

05Can an AI screening agent auto-reject candidates on its own?+

Greenhouse and Bullhorn will let it, so the rule has to come from your agency. What holds up under compliance review is ranked-with-reasons. Your agent shows its shortlist and reasoning, and a recruiter makes the call.

06Which firms build custom tools that integrate with Bullhorn, Avionte and Greenhouse?+

Pick a firm that can show working access to each system, a written integration spec and named write-back behaviour. That means Bullhorn OAuth keys, Avionte account credentials or Greenhouse Harvest v3 credentials, with every field it reads and writes listed. Hashlogics confirms that access first and writes the spec inside a fixed-fee Blueprint, credited in full against the build. Delivery is fixed-price milestones you accept against written criteria.

By , CEO, HashlogicsUpdated
Start

Let’s deploy working AI into your business.

We build AI agents and automation, ship them into the tools you already run, then stay on under an agreed service level. A senior engineer reads every brief, and your call gets scheduled within 24 hours.

What happens next

  1. 01

    You send a brief or book a call

    Two minutes, whichever you prefer.

  2. 02

    A senior engineer replies within 24 hours

    Not a sales rep.

  3. 03

    Honest scoping, in writing

    And if we’re not the right fit, we say so.

Abdul Basit, CEO of Hashlogics

“I started Hashlogics because too many teams ship a demo, get paid, and disappear. We build to a standard we’d run ourselves — and we stay to keep it running.”

Abdul Basit · CEO · a direct line

Not ready to talk? Take the checklist.

12 questions to ask any AI agency before you sign. They separate a demo shop from a team that ships to production.

Get the checklist

Free · no newsletter