# Dubbs Enterprises — POS platform API > One API runs a whole business: the register, the booking calendar, the customers, the > staff, the books and much more. Every screen we ship is built on it, and so is > everything below. If you can make an HTTP request, you can build on it too. This page > says who we are, what has already been built, how the API works and how to make your > first call. ## 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`). ### A 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`). ### A 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. ### An 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). ### A 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. ### Books 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. ### Short-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. ### Construction 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. ### A 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. ### Your 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:///pos/modules//api/index.php?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: - **Sales**: The Sales API is the point-of-sale register of a company: it rings up sales, takes payments, saves receipts, and handles returns and exchanges. - **Calendar**: The Calendar API holds a business's appointments: who is booked with which staff member, when, for which services, and at what price. - **Customers**: The Customers API keeps a business's customer records: who the customers are, how to reach them, their addresses, their services, and the links between family members' accounts. - **Employees**: This API holds a company's staff: their logins, profiles, working hours, services, days off, time clock, addresses and per-employee permissions. - **Inventory**: Inventory keeps a company's catalog: the products and services it sells, their stock counts, and the lists that describe them (categories, brands, departments, suppliers and their addresses, tax groups). - **Companies**: The Companies API is the record of every business on the platform: its company row, its place in the parent and subsidiary tree, its preferences and settings, its office addresses, its business hours and its storefront data. - **Bookkeeping**: Bookkeeping keeps a company's books: its bank and card accounts, every transaction, rental properties and their units, rent received, customer jobs, and the tax returns built from all of it. - **PropertyManagement**: This API runs a company's short-term rentals: the stays booked on its units (read from each unit's AirBnB, VRBO or direct-booking calendar feed), the cleaning after each stay with its photo proof and pay, and the listings and stay requests of its own booking site. - **Projects**: The Projects API keeps a company's projects: building and renovation jobs, field-service work and capital items, each with an address, a status, milestones, a scope of work, vendor quotes and, for a building, its 3D model. - **Jobs**: This API holds a company's job listings: the openings it advertises, each with a title, a description, a salary, a status (active or inactive) and a location. - **BusinessIntelligence**: The Business Intelligence API serves the reports a company's managers read about their business. - **Mailer**: The Mailer API sends a business's emails and text messages: appointment notices, reminders, campaigns to its customer list, outreach, documents, and the messages its website forms produce. - **NotificationProviders**: This API holds each company's accounts with outside messaging and AI services (email, SMS, voice, text-to-speech, Google Gemini), and decides which account sends which kind of message. - **Deliveries**: Deliveries records stock arriving from a supplier: who sent it, when it was ordered, shipped and received, the invoice, and each item with its quantity and prices. - **ImageManagement**: ImageManagement stores and serves the suite's files: the pictures in every picture slot (a customer's photo, an item's picture, a company's logo and page images), videos, documents filed under a project, contact or customer service, and the platform's ISO, firmware and device-config library. - **IPTVGuide**: IPTVGuide is the back end of an IPTV (internet television) service. 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 1. **Get a key.** Access is by API key, issued to a company by Dubbs Enterprises. 2. **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. 3. **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:///pos/modules/Calendar/api/index.php -d action=bookAppointment -d dry_run=1 -d customer_id= -d staff_id= -d selected_date=2026-11-07 -d selected_time=1000 -d service_ids= -d api_key=` 4. **The key decides the company.** You see and change only your company's records and those of its sub-companies. 5. **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=`. The modules are listed above. It is open to Dubbs Enterprises' own key. 6. **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.