Changelog
Back to All

Avionté API updates: October 2026

November 9th, 2026

In October 2026, we introduced several new Front Office endpoints and a new webhook event, expanded existing API functionality across jobs, placements, and departments, and resolved an issue with GEO code validation and handling. See the rest of the article for details.

Front Office

This section covers new Front Office endpoints and webhook functionality, enhancements to existing endpoints, and a fix for GEO code validation.

New Endpoints

New Events

Enhancements

  • Get a Job Now Returns Representative Users from Oldest to Newest 182797

    The Get a Job endpoint now returns the representativeUsers array ordered from the oldest owner associated with the job to the newest, matching the order displayed in the BOLD UI.

  • Create a Job and Update a Job Endpoints Now Support Multiple Job Owners

    The Create a Job and Update a Job endpoints now support adding multiple job owners through the API, eliminating the need to add additional owners manually.

  • Create a Job and Update a Job Now Support Primary Job Description Selection

    The Create a Job and Update a Job endpoints now support an optional isPrimary query parameter to control whether the job description is marked as primary. The parameter defaults to true, matching BOLD UI behavior. When isPrimary=false, the job description is saved but not marked as primary.

  • Placement Endpoints Now Support Currency and Performance Information

    The following endpoints now include currency, performance, and performanceId in their 200 responses:

    The following endpoints support these properties in requests and responses:

    The currency property specifies the currency in which the placement's rates are quoted (USD or CAD). The performanceId property identifies the performance entry, and performance specifies the performance rating recorded for ending the placement.

  • Get Placement End Reason Definitions Now Supports Archived Records and Additional Properties

    The Get Placement End Reason Definitions endpoint now supports the optional includeArchived query parameter, which determines whether archived placement end reasons are included in the response.

    The 200 response now includes the following optional properties:

    • createTimesheet, which indicates whether ending a placement with this reason allows a timesheet to be created.
    • isArchived, which indicates whether the placement end reason is archived.
    • keepPositionFilled, which indicates whether ending a placement with this reason keeps the job's position filled.

  • Get Posted Jobs Now Indicates Indeed Apply Availability

    The Get Posted Jobs endpoint now includes the allowIndeedApply property in the 200 response. This property indicates whether applicants can apply to the job post through Indeed.

  • Get a Posted Job Now Includes Additional Applicant Settings

    The Get a Posted Job endpoint now includes the following properties in the 200 response:

    • allowIndeedApply, which indicates whether applicants can apply to the job post through Indeed.
    • requireResumeForWebApplicants, which indicates whether a resume is required for applicants submitting applications through the web.

  • Get a Department Now Supports Retrieving All Department Addresses

    The Get a Department endpoint now supports the optional includeAllAddresses query parameter, which indicates whether all department addresses are included in the response.

Fixed

  • GEO Codes Were Not Properly Validated or Saved Through the API

    Resolved an issue where geoCode values 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 Post a Talent and Patch a Talent endpoints now validate a provided geoCode against the city, state, and ZIP code. If the geoCode is valid, it is saved to the record. If the geoCode is invalid for the provided address, the API returns a 400 Bad Request response with an appropriate validation message.

    If geoCode is blank or null, validation is skipped.