https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39199 --- Comment #13 from David Cook <dcook@prosentient.com.au> --- (In reply to Shi Yao Wang from comment #12)
(In reply to David Cook from comment #10)
Possibly yeah. Could you describe your use case more?
It sounds to me that you're after something more like "GET /patrons/{patron_id}/notices" for an API endpoint? So the file would be api/v1/swagger/paths/patrons_notices.yaml. You'll have to remember to honour things like Library Groups (so using something like Koha::Patrons->search_limited(). We have to make sure that API endpoints mimic the behaviour of the .pl controllers. Of course, that's easier said than done for a lot of API scenarios... but yeah describe it a bit more.
It's really just getting the data necessary to show a user it's notices like in notices.pl but with an api call instead so I think your intuition is correct. I think I'll create another bug specifically for GET route
So that use case is interesting. I note that you said "to show a user its notices like in notices.pl". At the moment, Koha only supports the client credentials grant for OAuth (and the HTTP Basic Auth is basically the same thing). At some point, we need to start thinking about an API path starting with something like "/my/" where the API is in the context of the user rather than an all powerful API user. I raised bug 41671 to talk about / explore this -- You are receiving this mail because: You are watching all bug changes.