Avionté API updates: June 2026

In June 2026, we implemented a breaking change and delivered several fixes across the Front Office and Back Office APIs. See the rest of the article for details.

Front Office

This section covers Front Office API updates, including a breaking change, a new endpoint, and fixes to improve endpoint reliability and data retrieval.

Breaking Changes

The Create a Department Address and Update a Department Address endpoints no longer accept Main as a valid addressType value. Requests that submit Main as the addressType value now return a 400 Bad Request response.

The following addressType values are accepted:

• Worksite
• Billing

A department’s main address should be submitted through the address fields of the Add a Department and Update a Department endpoints. Creating or updating a separate Main address through the Department Address endpoints is longer supported.

This change aligns Department Address API behavior with how department addresses are managed in BOLD, ensuring a more consistent and reliable experience across the platform.

Fixed

• Query Multiple Jobs Returned Intermittent 504 Timeout Errors

  Resolved an issue where Query Multiple Jobs could return intermittent 504 Gateway Timeout errors when processing requests. Previously, some requests could time out before a response was returned.

  With this fix, the endpoint now processes requests more reliably, reducing timeout occurrences and improving overall endpoint stability.

• Get Talent Questionnaire Returned Incomplete Results for Job Board Submissions

  Resolved an issue where the Get a List of Talent Questionnaires endpoint returned only a portion of a completed questionnaire when the questionnaire was submitted through the job board. Previously, some questionnaire responses could be omitted, resulting in incomplete results being returned by the endpoint.

  With this fix, the endpoint now returns the complete set of questionnaire questions and answers regardless of how the questionnaire was submitted, including job board, API, and manual submissions.

• Add a Placement Failed When Time Approver Had No BOLD User Record

  Resolved an issue where the Add a Placement endpoint could fail if the specified time approver (timeApproveId) did not have a corresponding BOLD user record. Previously, placement creation could not be completed unless the time approver already existed as a user.

  With this fix, if the specified time approver does not have a BOLD user record, the system automatically creates one before creating the placement. If the user record already exists, the placement is created successfully without modifying the existing user record.

• talent_tag_deleted Webhook Event Was Not Triggered for Several Talent Tag Removal Endpoints

  Resolved an issue where the talent_tag_deleted webhook event was not triggered when the following endpoints were used:

  • Remove Company Experience
  • Remove Talent Tag
  • Remove Talent Source
  • Remove Industry Experience
  • Remove Talent Quick Title
  • Remove Citizenship
  • Remove Certification

  With this fix, the talent_tag_deleted webhook event is now triggered for deletions made through any of these endpoints. When multiple deletions occur as part of a single operation, the event is triggered only once.

Back Office

This section covers a Back Office API update to improve endpoint behavior.

Fixed

• Get Talent Benefit YTD Summaries Returned Incorrect Success Status Code

  Resolved an issue where the Get Talent Benefit YTD Summaries endpoint returned a 201 Created response instead of the expected 200 OK response when requests completed successfully.

  With this fix, the endpoint now returns a 200 OK response.