Changelog
Start typing to search…
Back to All

Avionté API updates: November

December 8th, 2025

In November 2025, we introduced a new event along with several enhancements and fixes across the Front Office API. Click the title to view the complete update.

Front Office

New Event

  • job_skills_updated
    This event is sent whenever job skills are added, updated, or removed. This includes changes made in the BOLD UI under Job > Position Categories and Skill Set as well as updates made through the Add Job Skills and Remove Job Skills API endpoints.

Enhancements

  • The Get a Company endpoint now includes two new properties: isParent and parentCompanyId. The isParent property indicates whether the company is a parent company, and parentCompanyId provides the identifier of the parent company when the requested company is a Standard (non-parent) company, if available. For parent companies (isParent = 1), this value is always empty.

    This enhancement applies to tenants using the Company Types feature in BOLD.

  • The Get Background Checks endpoint now includes a new property, backgroundCheckId, which provides the unique identifier for the background check record.

  • The Patch a VMS Job endpoint has been enhanced to ensure that updates sent through the endpoint are reflected in BOLD’s External Job Staging screen.

    When a VMS job that was created and staged in BOLD receives updates to status, position count, or VMS Notes, the updated values will now appear in the External Job Staging screen.

Fixed

  • Talent Did Not Display in Pipeline When jobActivityTypeId Not Provided

    Resolved an issue where the Add Talent to Pipeline Stage endpoint required a jobActivityTypeId for the talent to appear in the Pipeline grid in BOLD.

    Previously, if the jobActivityTypeId field was left empty, the record was saved in the database but not displayed in the Pipeline. With this fix, the system now correctly includes those records, and the talent added without a jobActivityTypeId are visible in the Pipeline stage and corresponding Pipeline bucket in BOLD.

  • Incorrect Timestamp Used for Contact Activities
    Resolved an issue where the Create Contact Activity endpoint recorded the contact’s last activity timestamp as the time the API call was made, rather than using the value provided in the activityDate parameter.

    With this fix, the system now correctly applies the UTC datetime specified in the activityDate parameter when updating the contact’s last activity.

  • All Job Notes Updated Instead of Latest Only

    Resolved an issue where calling the Update a Job endpoint with a value in the notes property caused all job notes to be updated to the same text.

    With this fix, the endpoint now updates only the most recent job note to the value provided in notes. All previous notes remain unchanged. If notes is not provided in the payload, existing notes are not modified.

  • Document Type Ignored When Uploading Job Documents

    Fixed an issue where the Upload a Document to Job endpoint always saved uploaded documents with a Standard document type, even when a different documentType was provided in the payload.

    The endpoint now correctly applies the document type specified in the request, supports custom document types configured in the UI, and defaults to Standard only when no type is provided or the specified type is not valid for the tenant.

  • Department Address Could Not Be Created When Using an Existing Address
    Resolved an issue where the Create a Department Address endpoint prevented users from creating a worksite or billing address when the same address was already associated with the department, returning a Department address already exists error.

    The endpoint now allows creating additional address types using the same address, matching the behavior of the BOLD UI.

  • Talent Created via WebApply API Did Not Trigger talent_created Event
    Resolved an issue where talent created through the WebApply API did not trigger a talent_created webhook event.

    With this fix, when new talent is created through the WebApply API, the system now sends the appropriate webhook notification to subscribed endpoints.