Add PAPI methods to edit Patron Information
The ability to edit patron information—such as custom data fields or core registration details like name and email—without requiring the patron’s PIN or password would be highly beneficial. While using a Record Set to bulk edit standardized fields (e.g., expiration date or User1–User5) is extremely helpful, it doesn't cover all use cases.
For example, we regularly receive updated information from our partner school, including address changes. Currently, the inability to programmatically update these records creates workflow bottlenecks and limits our efficiency in maintaining accurate patron data.
[Deleted User]
shared this idea
-
AdminSamantha Quell
(Admin, Innovative)
commented
Wes is correct that staff authentication would allow you to perform more edits to patron records via PAPI.
We also expanded the support for address modifications in the v2 endpoints for PatronRegistrationCreate and PatronRegistrationUpdate, because we received feedback from third-party address verification services that they were limited in writing back changes to the database.
I'm going to close this request as already supported for the basic patron updates via staff authentication.
There is a separate request that I will link here for anyone following at home to add the custom data fields into PAPI: https://ideas.iii.com/forums/951742/suggestions/49518215
-
Wes Osborn
commented
If you authenticate as a staff member, you should be able to use API methods that would normally require a patron PIN: