Bullhorn REST API: parse a resume file into structured Candidate data
domain: bullhorn.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate and obtain a BhRestToken as usual.
POST the resume file as multipart/form-data to {corporation-token}/resume/parseToCandidate?format=html (or format=text), matching the input format to the file content.
Optionally add populateDescription=html (or text) to have the parsed content also placed into the Candidate description field.
Read the unsaved Candidate-shaped JSON in the response (work history, education, contact fields) rather than a persisted record.
Use the parsed fields as the body for subsequent PUT calls to entity/Candidate, entity/CandidateWorkHistory, and entity/CandidateEducation to actually save the parsed data.
For pasted text instead of a file, call parseToCandidateViaJson with the text as a JSON-encoded string body instead of a multipart upload.
Known gotchas
parseToCandidate only returns unsaved data — it does not create the Candidate record; you must make separate PUT calls to persist the parsed fields.
The format parameter must match the actual input encoding (html vs text); mismatches degrade parsing quality.
Resume parsing is a metered/licensed feature on some Bullhorn contracts — confirm entitlement before building volume workflows around it.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?