feat(api): keyless public booking read-back for guests #19
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/public-booking-status"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Keyless GET /api/v1/public/bookings/{id} so a guest can read back their own booking over HTTP. The existing booking read needs a wallet invoice key, so the webapp's booking dialog had to poll the invoice on LNbits core, which only says "paid", not "confirmed".
The booking id from the quote is the capability, same trust level as the RPC door's chatelet_booking_get. The response is public_booking_dict: lifecycle, dates and money only; guest pubkey, contact, payment hash and the Nostr event ids are stripped.
Tests cover the strip, the 404 and the happy path. Consumer: aiolabs/webapp#154.
Closes #18