Booking and scheduling
FreeSystem map@rabbinatix/booking-architecture by Rabbinatixupdated Oct 13, 2026
Customers pick a free time slot and book it; the backend holds the slot, takes a deposit, syncs the calendar and sends reminders.
7 systems and 11 APIs. Every API is declared on both sides, so every contract starts healthy. Rename or change anything once it is on your map.
6 connections · 11 APIs
- Booking Site → Booking API
POST /api/v1/auth/registerCreate an accountPOST /api/v1/auth/loginLog in with email and passwordPOST /api/v1/auth/logoutLog outGET /api/v1/availabilityFree slots for a service on a dayPOST /api/v1/bookingsBook a slotDELETE /api/v1/bookings/{id}Cancel a booking
- Staff App → Booking API
POST /api/v1/auth/registerCreate an accountPOST /api/v1/auth/loginLog in with email and passwordPOST /api/v1/auth/logoutLog outDELETE /api/v1/bookings/{id}Cancel a bookingGET /api/v1/staff/me/bookingsMy bookings for a day
- Reminder Worker → Booking API
GET /internal/v1/bookings/upcomingBookings that need a reminder
- Booking API → Calendar API
POST /calendars/{calendarId}/eventsPut the booking in the staff calendar
- Booking API → Payment Provider
POST /v1/paymentsTake the deposit
- Reminder Worker → SMS API
POST /v1/messagesText a reminder
Systems (7)
Booking Site
Where customers find a time and book.
Staff App
Where staff see and manage their day.
Booking API
Services, staff, opening hours and bookings.
Reminder Worker
Sends reminders before each booking.
Calendar API
Staff calendars, like Google Calendar or Microsoft 365.
Payment Provider
Takes the deposit.
SMS API
Text reminders, like Twilio.
A system you already have under the same name is used, not copied. Outside APIs don't count towards your plan.
Also as a flow
Also as a whiteboard
Versions
