https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24599 Martin Renvoize <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|koha-bugs@lists.koha-commun |agustinmoyano@theke.io |ity.org | -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24599 Arthur Suzuki <arthur.suzuki@biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arthur.suzuki@biblibre.com --- Comment #1 from Arthur Suzuki <arthur.suzuki@biblibre.com> --- Hi, IMO that case should be handled by the api client in a loop with multiple call. Since the status of the reply provides information about the success (or failure) of the reservation, either we would need to make a whole new api endpoint, or a breaking change in the format of both the call and the reply. Breaking change are always a bad thing, especially when it comes to API used by other software in the wild (VuFind, Aspen, Bokeh, Summon, etc...). Arthur -- You are receiving this mail because: You are watching all bug changes.