Bullhorn REST API: upload and retrieve file attachments on an entity
domain: bullhorn.com · 5 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.
Upload a file with PUT {corporation-token}/file/{entityType}/{entityId}, sending a JSON body with fileContent (base64), fileType, name, contentType, description, and type.
Alternatively use the multipart/form 'raw' file request variant for direct binary upload without base64 encoding.
List attached files' metadata with GET {corporation-token}/entity/{entityType}/{entityId}/fileAttachments (contentType, dateAdded, fileSize, fileType fields).
Download a specific file's content with GET {corporation-token}/file/{entityType}/{entityId}/{fileId}, optionally adding the raw path parameter to get a browser-downloadable multipart response.
Known gotchas
The older /entityFiles/{entityType}/{entityId} endpoint is deprecated in favor of /entity/{entityType}/{entityId}/fileAttachments — don't build new integrations against it.
Files can only be attached to a specific set of entity types (BillableCharge, Candidate, ClientContact, ClientCorporation, JobOrder, Opportunity, Placement) — confirm your target entity is supported before uploading.
Base64 file content payloads count against request size limits; large resumes/documents may need the raw multipart upload path instead.
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?