We use ChargeBalance, StatisticalClassID and BirthDate with 3rd party vendors to verify if our patrons are eligible to use licensed resources. Currently if I have a 3rd party vendor use PAPI to auth our patrons I would have to have them use PatronBasicDataGet to access this data which also returns personal information I do not want them to have access too. If ChargeBalance, StatisticalClassID and BirthDate were added to PatronValidate then the 3rg party vendors would not have unnecessary access to the full patron record. It may also be beneficial to include the UDF fields, Patron Name and email address as these could help populate the account creation form with the 3rd party vendor. I would also be open to adding a new endpoint that is truly basic patron data.