Avionté bug fixes: Week of August 17, 2026
This update addresses several issues affecting API data validation, placement updates, and webhook event behavior. Check the rest of the article for more details.
-
GEO Codes Were Not Properly Validated or Saved Through the API
Resolved an issue where
geo_codevalues provided through the API were not consistently validated or saved. Previously, valid GEO codes could be omitted from the corresponding records, and invalid GEO codes could be accepted for the provided address.With this fix, the Create a Talent, Update a Talent, Create a Company, Update a Company, Add a Department, and Update a Department Address endpoints now validate a provided
geo_codeagainst the city, state, and ZIP code. If thegeo_codeis valid, it is saved to the record. If thegeo_codeis invalid for the provided address, the API returns a400 Bad Requestresponse with an appropriate validation message.If
geo_codeis blank or null, validation is skipped. -
Add a Placement and Update a Placement Did Not Set Time Approvers
Resolved an issue where the Add a Placement and Update a Placement endpoints did not correctly set time approvers in BOLD when
timeApprovedUserIdswas provided. Previously, the time approvers specified in the request were not applied to the placement.With this fix, the endpoints now set the time approvers specified in the
timeApprovedUserIdsarray when creating or updating a placement. The request returns an error if a specified time approver's company does not match the job's company. -
talent_tag_added Webhook Event Was Not Triggered for Talent Tag Additions
Resolved an issue where the talent_tag_added webhook event was not triggered when the following items were added from the Talent > Custom Fields tab (or the Talent > Tags tab for accounts not integrated with Back Office):
- Standard Tags
- Applicant/Talent Tags
- Industry Experience Tags
- Applicant Sources
- Custom Tags
- Certification (customizable tag)
- Citizenship (customizable tag)
- Quick Search (customizable tag)
- Company Experience (customizable tag)
With this fix, the event is now triggered when these items are added through the UI. The corresponding API issue was resolved in the July 2026 release. When multiple items are added as part of a single operation, the webhook is triggered only once.
