SalonRunner API
SalonRunner is a cloud-based, privately branded salon and spa management platform built from the ground up as a multi-tenant web application. This page is an independent design exercise that asks what a well-designed SalonRunner API could look like: the resources it would expose, the authentication it would need, and the workflows it could unlock. Below: a hypothetical endpoint design, the technical requirements a production implementation would face, the use cases programmatic access could serve, and where to start if your team needs this kind of access today.
This page is an independent analysis by Supergood of what a well-designed SalonRunner API could look like. It draws on publicly available information, vendor materials, and general integration experience in this category. Nothing on this page describes an existing SalonRunner product, and Supergood is not affiliated with or endorsed by the vendor. If the vendor offers an official API, we highly recommend it.
What is SalonRunner?
SalonRunner is a cloud-based, privately branded salon and spa management platform built from the ground up as a multi-tenant web application. Salons and spas use it to let clients book their own appointments online, ring up sales at the point of sale, track inventory in real time, manage staff and schedules, and run client communications and marketing, all accessible from any device through a fully responsive web app.
Core product areas include:
- Online Client Scheduling (clients self-book and view service, product, and gift card history via web, social, or mobile web app)
- Point of Sale (ring up sales, manage the cash drawer and transaction types, with integrated credit card processing on any device)
- Inventory Management (real-time tracking that adjusts on sales, returns, and receipts with low-stock trigger alerts)
- Employee Management (staff scheduling and access)
- Client Connect (Enhanced SMS, Text Confirmations, Client Images, Image Library, Mass Emails, and Automated Emails)
- Marketing and eCommerce (targeted campaigns and online product/gift card sales)
- Advanced Reporting (sales, inventory, and client analytics)
An API for a platform like this would naturally organize around its core data entities:
- Appointments, Services, Service Providers, Availability
- Clients, Client Images, Service and Product History, Notes
- Sales, Transactions, Payments, Cash Drawer
- Products, Inventory Levels, Receipts, Returns
- Gift Cards and Balances
- Employees, Schedules, Roles
- Email and SMS Campaigns, Automated Messages
The SalonRunner Integration Challenge
Salons and spas run daily operations on SalonRunner, but turning its web- and mobile-driven workflows into API-driven automation is non-trivial:
- No public API: SalonRunner does not publish developer documentation or expose a public, programmatic interface, data lives behind the authenticated web and mobile app
- Private branding per tenant: The product is privately branded per salon, so portal URLs, theming, and entry points vary across deployments
- Mobile-web access patterns: Much of the booking and checkout experience runs through the responsive mobile web app, complicating headless automation
- Session-bound data: Appointments, client history, and gift card balances are only reachable inside an authenticated session that must be maintained and refreshed
- Real-time inventory coupling: Stock figures adjust on every sale, return, and receipt, so reads and writes must respect live inventory state and trigger points
- Payment and gift card sensitivity: Point-of-sale transactions, integrated card processing, and gift card balances demand careful, idempotent handling
What a SalonRunner API Could Look Like
If SalonRunner exposed a modern, general-purpose API, the integration challenges above suggest what it would need to get right. This is a design sketch, not documentation of anything that exists today:
- First-class authentication: session handling with support for MFA and enterprise sign-on where the platform uses them
- Consistent resources: normalized JSON schemas and pagination across the platform's core objects
- Reliable writes: idempotency keys and validation that mirrors the platform's own workflow rules
- Entitlement awareness: endpoints scoped to what each customer's licensing actually permits
The endpoint sketches, technical requirements, and use cases below flesh out this hypothetical design.
How AI agents could connect to software like SalonRunner: MCP servers for software without a public API →
Need This Kind of Access Today?
If your team needs this kind of access today, Supergood builds integrations on request, one customer at a time. We act at the direction of our customers, within the access they already hold. Customers bring their own accounts, licenses, and entitlements. If the vendor offers an official API, we highly recommend it.
- Schedule an Integration Assessment
A 30-minute session to review your product mix, licensing, and authentication model. - Scope the Integration
We design the access pattern around your workflows and entitlements. - Deploy with Monitoring
Go live with continuous monitoring as your platforms evolve.
Potential API Endpoints
Authentication
/authenticateWould authenticate to a SalonRunner account using username/password and any MFA challenge, returning a session token for downstream calls.
Scheduling
/appointmentsWould list appointments with filters for date range, service provider, client, and status.
Scheduling
/create_appointmentWould book a new appointment for a client against a service, provider, and available time slot.
Clients
/clientsWould retrieve client records including profile, service and product history, notes, and gift card balances.
Point of Sale
/create_saleRing up a point-of-sale transaction with services, products, payments, and gift card redemption.
Inventory
/inventoryWould pull real-time product inventory levels, low-stock alerts, and recent receipts and returns.
Use Cases
Sync appointments and client data into your stack
- Pull appointments, providers, and availability into a central calendar or warehouse - Reconcile client profiles, service history, and notes across marketing and CRM tools - Surface gift card balances and visit history for a unified client view
Automate booking and reminder workflows
- Create and reschedule appointments programmatically without portal clicks - Trigger Enhanced SMS and email confirmations and reminders from external systems - Route no-show and cancellation events to retention and rebooking flows
Reconcile point-of-sale and inventory
- Stream sales, payments, and gift card redemptions into accounting and BI - Match real-time inventory adjustments against receipts, returns, and low-stock triggers - Reconcile integrated credit card transactions with daily cash-drawer totals
Power client marketing and analytics
- Export client segments to drive Mass Emails and Automated Emails campaigns - Feed advanced reporting data into external dashboards - Sync product and service catalogs to eCommerce and loyalty tools
Connect via No-Code Tools
Automate this platform from the no-code stack you already use.
Technical Requirements
Authentication
Would require username/password and MFA challenges with managed session handling
Connectivity
Would build on authenticated web and responsive mobile-web flows, derived from the privately branded portal
Response format
Normalized JSON across Appointments, Clients, Sales, Inventory, and Gift Card objects
Rate limits
Adaptive throttling tuned to your account to avoid platform-side limits
Session management
Would need automatic session refresh, MFA replay handling, and credential rotation
Data freshness
Near real-time pulls for appointments, sales, and inventory with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for new bookings, cancellations, checkouts, and low-stock alerts
Latency
Design target: sub-second reads on cached entities; multi-second writes when posting bookings and sales
Throughput
Design target: horizontally scaled workers sized to multi-location appointment and transaction volume
Reliability
Retry, backoff, and idempotency keys for bookings, sales, and gift card transactions
Versioning
Clear versioning and change management would matter as SalonRunner evolves
Frequently asked questions
Yes. The adapter is configured to your salon's branded SalonRunner portal, handling its specific URLs, theming, and entry points while returning consistent normalized objects.
Sales, payments, and gift card redemptions are exposed alongside real-time inventory levels. Writes are idempotent and retry-safe so checkouts and stock adjustments stay consistent with live state.
Availability of official interfaces varies by product, plan, and licensing. Many platforms in this category gate access behind partner programs or paid modules, and there is often no broadly available, self-serve public API. Check the vendor's developer resources for current offerings.
The hard parts would be authentication (MFA, session management, enterprise controls), consistent schemas across the platform's products, and write semantics that reconcile the way the platform's own workflows do.
No. This page is an independent analysis by Supergood and is not affiliated with, sponsored by, or endorsed by the vendor. All product names and trademarks belong to their respective owners and are used for identification only. Nothing here documents an actual SalonRunner product or service.
Supergood acts at the direction of its customers, within the access those customers already have. We respect each customer's agreements with their software vendors, and how those agreements apply to a customer's use is a determination the customer makes. If the vendor offers an official API, we highly recommend it.
Supergood builds managed API access to enterprise software for customers on request, scoped to each customer's own licensing and entitlements. If your team needs programmatic access to a platform like this, schedule an integration assessment to discuss options.