Bug 24260 - REST Self Registration
Summary: REST Self Registration
Status: RESOLVED DUPLICATE of bug 30299
Alias: None
Product: Koha
Classification: Unclassified
Component: REST API (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low new feature
Assignee: Lari Taskula
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-18 10:50 UTC by Lari Taskula
Modified: 2025-10-21 19:51 UTC (History)
2 users (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: Sponsored
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lari Taskula 2019-12-18 10:50:03 UTC
Support self registration via REST API
Comment 1 Arthur Suzuki 2022-07-28 12:24:14 UTC
This sounds like doing :
<pre>
curl -X POST https://demo.biblibre.com//api/v1/patrons \
    -H 'Authorization: Basic [your-token]' \
    -d '{
    "address":"anywhere",
    "city":"nowhere",
    "firstname":"asu",
    "surname":"zuki",
    "library_id":"SITE",
    "category_id":"ADULT"
}'
</pre>

to me the only bug we have here is, the post patron api doesn't use the self-registration prefs like PatronSelfRegistrationDefaultCategory.
It means the category is mandatory, where it is not when using the OPAC.
Comment 2 Katrin Fischer 2023-12-31 11:29:13 UTC
> 
> to me the only bug we have here is, the post patron api doesn't use the
> self-registration prefs like PatronSelfRegistrationDefaultCategory.
> It means the category is mandatory, where it is not when using the OPAC.

It's a little more than that. If you use email verification, which you should, then you'd want the patrons to be added to the borrower_modifications table first, not directly into the borrowers table.
Comment 3 Andrew Fuerste-Henry 2025-10-21 19:51:30 UTC
I'm marking this as a dupe of 30299, even though this is the older bug. 30299 has a bit more detail on it.

*** This bug has been marked as a duplicate of bug 30299 ***