Avionté bug fixes: Week of October 12, 2026

This update addresses issues with GEO code validation and handling when creating or updating talent records through the API. Check the rest of the article for more details.

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.