Avionté API updates: August 2026
In August 2026, we introduced new endpoints and webhook events, added an enhancement, and released several fixes to API functionality. See the rest of the article for details.
Front Office
This section covers Front Office API updates, including new endpoints, an enhancement, a new webhook event for talent resume tags, and several fixes to improve API reliability, data handling, and webhook behavior.
New Endpoints
- Create Placement Export Request
Submits an asynchronous request to export placement data for the given tenant. - Get Job Order Templates
Returns all job order templates for the tenant. - Get Submitter Terms
Returns the account's configured timesheet Submitter Terms configured under Accounts & Settings > Utilities. - Get Approver Terms
Returns the account's configured timesheet Approver Terms configured under Accounts & Settings > Utilities.
New Events
- talent_resume_tag_added
Thetalent_resume_tag_addedevent is sent when a resume/CV tag is added to a talent profile through Add Talent Resume Tags or on the Talent > Custom Fields/Tags tab.
Enhancements
- The Create a VMS Job endpoint now supports the
jobTemplateIdproperty, which identifies the job order template to associate with the VMS job.
Fixed
-
Query Multiple Talents Returned Intermittent 504 Timeout Errors
Resolved an issue where Query Multiple Talents could return intermittent
504 Gateway Timeouterrors 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.
-
Some Job Endpoints Did Not Process Plain Text Job Descriptions
Resolved an issue where the Create a Job, Update a Job, and Create a VMS Job endpoints did not correctly process plain text job descriptions. Previously, when a description was included in the request, it was not saved to the job record and a job description document was not created.
With this fix, plain text job descriptions are now saved to the job record, and a job description document is created when a description is provided.
-
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. -
Pipeline Stage Endpoints Did Not Save Message to Talent Activity Notes
Resolved an issue where the message field provided through the Add Talent to Pipeline Stage and Update a Talent Pipeline Stage endpoints was not saved to the talent's activity notes. Previously, the message value was returned in the API response but did not appear in the Notes/Comments field in the UI.
With this fix, the
messagevalue is now saved and displayed in the Notes/Comments field for the corresponding talent activity. The API response continues to return themessagefield. -
talent_tag_deleted Webhook Event Was Not Triggered for Talent Tag Deletions
Resolved an issue where the talent_tag_deleted webhook event was not triggered when the following items were deleted 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 deleted through the UI. The corresponding API issue was resolved in the June 2026 release. When multiple items are deleted as part of a single operation, the webhook is triggered only once.
-
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.
-
Back Office
This section includes a new Back Office webhook event for partner export processing.
New Events
- PartnerExportReadyEvent
ThePartnerExportReadyEventevent is sent when the requested partner export data is ready for retrieval.
