Quote from: doktornotor on September 09, 2024, 08:58:00 PM
Well, admittedly I never tried any API stuff with Kea, but 200 sounds like "it worked", not "failed".
200 might just mean it received the request and the API didn't know how to process the data so it reported back that it failed to create the reservation. When I look in the UI I don't see the reservation that it should create from the API request. I'm wondering if the data structure is missing something.