Avionté API updates: March 2026

In March 2026, we introduced new endpoints and webhook events in the Front Office API, along with several enhancements and a bug fix. See the section below for details.

Front Office

This section includes new endpoints and webhook events, as well as enhancements and a bug fix in the Front Office API.

New Endpoints

New Events

  • job_pipeline_talent_modified
    The job_pipeline_talent_modified event is sent after a job pipeline is updated.
  • job_pipeline_talent_removed
    The job_pipeline_talent_removed event is sent after a pipeline stage is permanently deleted.
  • placement_removed
    The placement_removed event is sent after a placement is deleted.
  • talent_nomination_updated
    The talent_nomination_updated event is sent after nomination status is updated for a talent.
  • talent_nomination_removed
    The talent_nomination_removed event is sent after a talent's nomination stage is permanently deleted.
  • web_applicant_submitted
    The web_applicant_submitted event is sent after a web applicant is nominated or pipelined.
  • web_applicant_updated
    The web_applicant_updated event is sent after a web applicant's pipeline or nomination stage is modified.
  • web_applicant_removed
    The web_applicant_removed event is sent after a web applicant's pipeline or nomination stage is permanently deleted.

Enhancements

  • The job_updated webhook event has been updated to trigger when the job owner is added, removed, or updated on a job record.

    With this update, the event now fires for these changes through both the UI and the Update a Job endpoint.

  • The placement_started webhook event payload now includes the TalentId parameter, representing the identifier for the talent in BOLD.

  • The Create a Company and Update a Company endpoints now accept the phoneNumber property in the request body.

  • The Update a Talent endpoint has been updated to allow updates when firstName, lastName, or emailAddress are not included in the request.

    When these fields are not included, the endpoint now checks whether they are already populated on the talent record. If a field is not present on the record, the update is allowed to proceed without requiring it. If the field is already populated, it must be included in the request or the update will be rejected.

Fixed

  • Add a Department Response Did Not Return weekEndDay and Incorrectly Stored stateProvince

    Resolved issues where the Add a Department endpoint did not return the weekEndDay value in the response when weekEndDate was provided in the request, and where the stateProvince value was not stored in the correct database column.

    With this fix, the weekEndDay field in the response now reflects the weekEndDate value submitted in the request, and the stateProvince value is correctly saved and returned in subsequent responses, including when retrieving the department using the Get a Department endpoint.