Who we are
Dubbs Enterprises is a Chicago company. It runs its own businesses on this platform, among them Lincoln Square Barber Shop on West Lawrence Avenue, open since 2009, and it hosts other companies on the same platform as tenants.
What you can build
Every one of these runs today on the same API you get, with nothing private behind it.
A booking website
A shop's own site where a customer picks a barber, a service and a time, and books it. The site lists the services and their prices (listBookableServices), finds open times (listAvailableSlots), and books, moves or cancels through Calendar (bookAppointment, rescheduleAppointment, cancelBookedAppointment). bookAppointment with dry_run=1 checks a time without booking it. Customers sign up or in through Customers (registerCustomer, signInCustomer) and see their own visits (getCustomerAppointmentHistory).
CalendarCustomersA staff calendar that stays in sync
Every barber's day, week and month in Calendar (getCalendarDayData, getStaffMonthCalendar), days off and blocked slots (setSlotAvailability), and each booking mirrored into the staff member's own Google Calendar and checked against it (verifyGoogleEvent). Confirmations and reminders go out by email and text on rules each shop sets, with every message kept and resendable in EmailHistory (getEmailHistoryList, resendEmail).
CalendarEmailHistoryA customer CRM
One profile per customer in Customers: contact details, addresses, communication preferences and visit history, with search (searchCustomers), duplicate merging (mergeCustomerData) and per-customer activity counts (listCustomersWithActivityCounts). Leads keeps prospects with a source, a score and a status (new, called, working, won or dead), fed by public zoning and property records, a web form or a person typing them in.
CustomersLeadsAn AI phone receptionist
A phone number that answers itself. The caller asks for a haircut on Saturday, and the receptionist checks the calendar and books it while they are still on the line. Built on RobotBooker (the phone line and the call log) and Calendar (the booking itself).
RobotBookerCalendarA point of sale
The register behind the counter: items, prices and tax groups from Inventory, and every sale, receipt and return in Sales. The same data feeds the reports in Reports, such as sales per hour and appointments per month.
InventorySalesReportsBooks that keep themselves
Bank and card transactions flow into Bookkeeping from linked bank accounts, and are sorted into income and expenses, with duplicates caught (duplicateCandidates). On top of that: cash flow by year (cashFlowOverview), where the money went (moneyMap), interest paid on cards and mortgages (interestPaid), properties with their units, bills and depreciation schedules, project profit and loss (getProjectPnl), and a personal financial statement (personalFinancialStatement). Tax returns come out as real IRS forms, filled in as PDF previews (irsFormPdf): the 1040 and its schedules, Schedule D and Form 8949, Form 7203, Form 8582, and the 1120-S with its K-1.
BookkeepingShort-term rental management
Properties, units and their booking calendars in PropertyManagement, synced from the listing sites' calendar feeds, with the cleaning after each stay, its photo proof and the cleaner's pay.
PropertyManagementConstruction projects
A build's plans, surveys, permits and budget in Projects, with its documents in ImageManagement: large plan sets go up page by page, and a 3D model, material takeoffs and walkthrough films live beside them.
ProjectsImageManagementA TV service
IPTVGuide is the back end of an internet TV service: the channel lineup, the programme guide, subscriber accounts, a reseller panel, a Fire Stick app and a web player.
IPTVGuideYour idea next
A customer app, a kiosk, a dashboard, a voice assistant, a report your accountant wants: if the data lives here, an API action already reads or writes it. The full list is one call away (below).
How the API is built
- Every area is its own module, with one entry point: https://<host>/pos/modules/<Module>/api/index.php?action=<action>
- One request does one action. Reads are GET; changes are POST with form fields.
- Every answer is JSON in one shape: {"success": true, "data": {...}} or {"success": false, "error": "..."}, with a matching HTTP status (400 bad input, 401 no or bad key, 403 not allowed, 404 not found, 409 conflict).
- Modules never reach into each other's data; they call each other through this same API. What you can call is exactly what the platform itself uses.
The main modules:
One back end serves many companies. A company can have sub-companies (its locations or subsidiaries), and every record belongs to exactly one company.
Your first call
- Get a key. Access is by API key, issued to a company by Dubbs Enterprises.
- Send the key as a field named api_key in the query string for GET, or as a form field for POST. Not as a Bearer header.
- Try it without changing anything. bookAppointment with dry_run=1 checks a time and answers what it would book, without booking:
curl -X POST https://<host>/pos/modules/Calendar/api/index.php -d action=bookAppointment -d dry_run=1 -d customer_id=<id> -d staff_id=<id> -d selected_date=2026-11-07 -d selected_time=1000 -d service_ids=<id> -d api_key=<your key>
- The key decides the company. You see and change only your company's records and those of its sub-companies.
- Find the actions. The API contract for a module, the actions it takes and what they answer, is at /pos/modules/Companies/api/index.php?action=getApiContract&module=<Name>. The modules are listed above. It is open to Dubbs Enterprises' own key.
- Read before you retry. If a write times out, read back whether it landed before sending it again.
This page: /developers for people, /llms.txt or /pos/llms.txt for programs, and /pos/ opened by any program.
Read the developer guide →