Current API allows the fetching of Eptura Profile ID based on passthrough of Email Address Attribute. We would like to pass across our unique employee identifier code (BRID) in place of Email Address to fetch the Eptura Profile ID for a variety of reasons where Email Address may not be matching, such as change of business entity, users changing their last name or rejoining the business etc. whereby email changes have API returning two different user records — one active and one historical and consequently cannot match the user returning in with error.