Actions87
- Appointment Actions
- Candidate Actions
- Company Actions
- Contact Actions
- File Actions
- Job Actions
- Job Submission Actions
- Lead Actions
- Note Actions
- Opportunity Actions
- Placement Actions
- Sendout Actions
- Task Actions
- Tearsheet Actions
Candidate → Update
AI-generatedSummary
Update a Candidate record by specifying its Bullhorn ID and providing fields to modify either as individual field-value pairs or as a JSON object.
Inputs
- Authentication — Select authentication method, either user credentials (email and password) or enterprise API key.
- Enable Operations Log — Option to emit audit log entries to a second output for every write operation, useful for maintaining an audit trail.
- ID (required) — The Bullhorn ID of the Candidate record to update.
- Input Mode (required) — Choose how to supply the update payload: either via UI field pairs or a JSON object.
- Data (JSON) — Provide update fields as a JSON object; fields with empty, null, or undefined are skipped. Numeric reference IDs are auto-wrapped as {id: number}. Applies when input mode is JSON.
- Fields — Specify multiple Bullhorn fields and their new values as field-value pairs. Only include fields to update. Applies when input mode is fields.
- Output Fields — Specify fields to include in every output item, merged into success, no-result, and error items.
Output shape
a single updated Candidate entity record including any custom output fields.
The update API succeeds even with an empty payload as a no-op. If "Enable Operations Log" is set, a second output stream emits audit log records for this update operation.
Examples
Example 1: Update candidate status with field pairs UI
Authentication: Enterprise Credentials; ID: 12345; Input Mode: Field Pairs; Fields: status = Active; Output Fields: id, status
Example 2: Update candidate via JSON object
Authentication: User Credentials; ID: 67890; Input Mode: JSON Object; Data JSON: {"status": "Inactive"}; Output Fields: id, status