Avionté API updates: April 2026

In April 2026, we released updates across the Front Office and Back Office APIs, including enhancements, validation updates, and bug fixes.

Front Office

This section covers Front Office API updates, including a breaking change, enhancements, and fixes across multiple endpoints and events.

Breaking Changes

Create a Department Address Now Enforces Address Field Validation

The Create a Department Address endpoint now requires valid values for street1, city, state_Province, country, and postalCode. Requests that omit these properties or provide invalid values now return a 400 Bad Request response.

Additional validation is now enforced for state and country values:

• country must be a valid two-character country code
• state_Province must be a valid two-character state code
• state_Province must be valid for the specified country

Enhancements

• talent_saved Event Expanded for Resume Changes

  The talent_saved webhook event has been expanded to trigger when a talent’s resume is added, updated, replaced, or deleted.

  With this update, the event now fires for resume-related changes including uploads, updates, deletions, duplicate merges, and generated resume documents.

• job_updated Event Expanded for Completed Status

  The job_updated webhook event has been expanded to trigger when a job moves to the Completed status.

  With this update, external systems now receive job_updated notifications when a job reaches Completed, providing more reliable job status tracking.

• Save Talent Direct Deposit Accounts Now Validates Accepted Values

  The Save Talent Direct Deposit Accounts endpoint now validates accepted values for accountType, amountType, and fundingType.

  With this update, requests that submit unsupported values for these properties will return a 400 Bad Request response, helping ensure direct deposit account data is submitted with valid and supported configuration values.

• Patch a Talent Supports Optional Requirement Validation

  The Patch a Talent endpoint now supports an optional useNewTalentRequirements query parameter to control whether New Talent Requirements configured in BOLD are enforced during partial updates.

  When useNewTalentRequirements is set to true or omitted, the endpoint applies New Talent Requirements in addition to its default required fields. When set to false, the endpoint bypasses New Talent Requirements and allows partial updates without enforcing those additional field requirements.

• billingAddress Property Removed from Company Endpoints

  The billingAddress property has been removed from the request and response bodies of the Get a Company, Create a Company, and Update a Company endpoints. This property was not functionally supported and did not persist data, so it has been removed to align the API with actual behavior.

  To manage billing addresses, use the Create a Department Address endpoint to create a billing address, Get a Department Address to retrieve billing address details, and Update a Department Address to update a billing address.

• Create Talent Job Activity No Longer Requires Pipeline or Nomination Stage

  The Create a Talent Job Activity endpoint no longer requires a talent to be in a pipeline or nomination stage for the specified job.

  With this update, talent job activities can now be created for valid talent and job records regardless of whether the talent has already been pipelined or nominated.

Fixed

• Get Talent Questionnaires Did Not Return Results Completed via Job Board Application

  Resolved an issue where the Get a List of Talent Questionnaires endpoint did not return questionnaire results completed through the BOLD job board application. Previously, only questionnaires completed via onboarding tasks or API submissions were returned.

  With this fix, the endpoint now returns all completed questionnaires regardless of how they were submitted, including those completed during job board applications.

• creditTo Value Ignored in Talent Pipelining and Nomination API Requests

  Resolved an issue where the Add Talent to Pipeline Stage and Add a Talent Nomination Stage endpoints ignored the creditTo value provided in the request and instead defaulted to the API caller’s user ID.

  With this fix, when a valid creditTo user identifier is provided, the system now assigns credit to the specified user, aligning API behavior with the UI. If creditTo is not provided or contains an invalid value, the system defaults to the job creator.

• Update a Company Returned 500 Error When IsDuplicateBypassed Was Set to True

  Resolved an issue where the Update a Company endpoint returned a 500 error when the isDuplicateBypassed parameter was set to true, which prevented updates from proceeding.

  With this fix, when isDuplicateBypassed=true, the update proceeds successfully even if a duplicate name condition exists. When the parameter is set to false or omitted, duplicate name validation behaves as expected and prevents the update if a conflict is detected.

• Get Available Talent Statuses Incorrectly Removed Default Statuses

  Resolved an issue where the Get Available Talent Statuses endpoint incorrectly removed default system statuses when the includeDuplicates query parameter was set to false, even when no duplicate status names existed.

  With this fix, default system statuses are only replaced when a duplicate custom status exists. If no duplicates are present, all system statuses are returned as expected.

• Onboarding Documents Endpoint Returned 500 Error for Certain Talent Records

  Resolved an issue where the Get Talent Adobe Onboarding Documents endpoint could return a 500 error when retrieving documents for talent records with large or high-volume document sets. Previously, requests could fail when the total document payload exceeded the maximum amount of data the endpoint could return in a single response.

  With this fix, the endpoint now supports optional page and pageSize parameters, allowing to retrieve onboarding documents in smaller result sets.

  Note: If a request fails when using a large pageSize, retry with a smaller value. The optimal pageSize depends on the size of the documents being retrieved. This endpoint also excludes records where isArchived=1 and files with names containing AUDIT.pdf.

• Get Company Restrictions by Company IDs Endpoint Returned 504 Timeout Errors

  Resolved an issue where the Get Company Restrictions by Company IDs endpoint intermittently returned 504 Gateway Timeout errors when processing large multi-query requests.

  With this fix, the endpoint now processes multi-query requests more reliably and returns responses within expected performance thresholds under normal load conditions.

• Talent Could Appear in Multiple Pipeline and Nomination Stages After API Updates

  Resolved an issue where talent moved between pipeline and nomination stages through the Add Talent to Pipeline Stage and Add a Talent Nomination Stage endpoints could remain visible in multiple UI buckets at the same time. Previously, talent moved through the API could continue to appear in a previous pipeline stage after being nominated, causing the talent to appear in both pipeline and nomination stages at the same time.

  With this fix, talent moved through the API is now removed from the prior pipeline bucket, so it appears only in its current active stage.

Back Office

This section includes Back Office updates related to benefit enrollment and supplier handling.

Enhancement

• Benefit enrollment endpoints have been updated to improve how the supplier is resolved when supplierGuid is not included in the request.

  With this update, supplier resolution now follows this logic when supplierGuid is not provided:

  • If one active assignment exists, the supplier for that assignment is used.
  • If multiple active assignments exist, the supplier for the assignment with the earliest start date is used.
  • If no active assignments exist, the system defaults to the talent’s home office supplier.

  If supplierGuid is provided in the request, the specified supplier is used directly.