Avionté API updates: October
In October 2025, we introduced multiple updates across both the Front Office and Back Office APIs. This release delivers several functional enhancements, a new endpoint, and key fixes that improve reliability, performance, and data consistency. Click the title to view the complete update.
Front Office
This section highlights recent improvements to the Front Office API, including a new endpoint, several functional enhancements, and fixes.
New endpoint
- Get User Types
Returns a list of configured user types for the tenant.
Enhancements
- The Update a Company endpoint now includes a new property,
isDuplicateBypassed, which provides greater control over duplicate name validation when updating company records.- If
isDuplicateBypassedis set totrue, the duplicate name check is skipped when updating the company name. - If set to
false, the duplicate name check is performed, and updates are restricted if another company with the same name exists. - If not provided, the standard duplicate check logic is triggered. If a duplicate company name is detected, the update is rejected and an appropriate duplicate name error message is returned.
- If
- The Create a VMS Job endpoint has been updated to include a new property,
isRequired, within thejobRequirementsobject. This property indicates whether a job requirement is required (true) or optional (false). For backward compatibility, the value defaults totruewhen not specified.
- The Create a Job, Update a Job, Get a Job endpoints have been updated to include a new property,
timeCaptureMethod. This property specifies how talent should log their time for a job. Possible values are: Timesheets, Daily_Time, Group_Time, Batch_Hours, and Mobile_Punch.
- The Add a Placement, Update a Placement, Get a Placement, Get Active Placements by Company IDs, Get an Extended Placement, and Query Multiple Placements endpoints now include a new property,
status, within theplacementScheduleShiftDtosandplacementScheduleShiftsobjects. The property indicates the current status of the placement schedule shift (Committed, Canceled).
- The Add Talent Skills, Get Talent Skills, Query Multiple Talent Skills, Remove Talent Skills, Add Job Skills, Get Job Skills, Query Multiple Jobs Skills, and Remove Job Skills endpoints now support a new property,
skillTalentFacing. The property indicates whether a skill is visible and applicable to talent users.
- The Get Skill Positions and Get Paged Skill Positions endpoints have been updated to include a new property,
talentFacing, which specifies whether a skill is visible and applicable to talent users.
Fixed
-
Get Placement IDs Endpoint Returned 504 Timeout Errors
Resolved an issue where the Get Placement IDs endpoint could return504 Gateway Timeouterrors. The underlying database query has been optimized to improve performance and reduce the likelihood of timeouts. In addition, the endpoint now applies a maximum page size of 100. If a larger value is passed in the request, it is automatically adjusted to 100 to help maintain stable and consistent performance. -
Credit To Value Did Not Match Payload
Resolved an issue where the Credit To value displayed in the UI did not match the
creditTovalue provided in the payload when using the Add Talent to Pipeline Stage endpoint.With this fix, when a valid user ID is passed in the
creditToproperty, the endpoint now correctly returns that same ID in the response, and Credit To column displays the corresponding username.If the
creditTovalue is not provided or the specified user does not exist in HCM, the system defaults to using the job owner as the Credit To value.
Back Office
This section highlights an enhancement to the Back Office API.
Enhancements
- The PayrollBenefitExportReadyEvent event now includes a new property,
ExportType, which specifies the type of data included in the export. Possible values are:PayrollBenefitDeductionExport: Indicates the export contains deduction data.PayrollBenefitContributionExport: Indicates the export contains contribution data.
