SimplyBook.me API
SimplyBook.me is a cloud-based appointment scheduling and online booking platform for service businesses. This page is an independent design exercise that asks what a well-designed SimplyBook.me 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 SimplyBook.me 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 SimplyBook.me 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 SimplyBook.me?
SimplyBook.me is a cloud-based appointment scheduling and online booking platform for service businesses. Clients book 24/7 across the company website, Facebook, Instagram, Google, and a branded app, while businesses manage staff availability, automated reminders, payments, and client history from one system. It serves beauty and wellness salons and spas first, alongside healthcare clinics, fitness and sports, education, professional services, and events.
Core capabilities include:
- Multi-channel booking with calendar sync, recurring and group bookings, and an AI voice booking assistant
- Automated email, SMS, WhatsApp, and Telegram notifications, reminders, and review requests
- Payment processing, POS, gift cards, coupons, memberships, and package management
- Custom intake forms (HIPAA and SOAP), client history, product sales, and loyalty tools
An API for a platform like this would naturally organize around its core data entities:
- Bookings, statuses, comments, and recurring settings
- Clients, client comments, and intake form data
- Services (events), service providers (units), durations, and pricing
- Availability, start-time matrices, working hours, and breaks
- Booking stats, revenue, top performers, and workload metrics
The SimplyBook.me Integration Challenge
Service businesses run their day on SimplyBook.me, but turning it into a reliable API-driven integration runs into several obstacles:
- Paid-feature gating: API access only exists once the paid API Custom Feature is enabled in the admin interface, so the integration surface is off by default
- JSON-RPC, not REST: Methods are invoked through JSON-RPC 2.0 envelopes across separate login, public, and admin services rather than conventional REST resources
- Short-lived tokens: Access tokens issued by getToken expire after one hour, requiring continuous re-issuance and rotation for headless automation
- Per-company keys: Each company tenant has its own API key, so multi-location operators must orchestrate credentials and tokens across many tenants
- Method sprawl: Over eighty admin methods span bookings, clients, catalog, availability, and reporting, with their own parameter shapes and ID conventions
- Booking-lifecycle nuance: book, editBook, and cancelBooking must respect availability, working hours, and status rules to avoid double-booking or invalid slots
What a SimplyBook.me API Could Look Like
If SimplyBook.me 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 SimplyBook.me: 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
/login/getTokenWould exchange your company login and API key from the API Custom Feature for a one-hour access token used on subsequent JSON-RPC calls.
Bookings
/admin/getBookingsWould retrieve a filtered list of bookings by date range, service, provider, client, or status, with details available via getBookingDetails.
Bookings
/admin/bookWould create a new booking for a given service (event), provider (unit), client, and time slot; editBook and cancelBooking manage the lifecycle.
Clients
/admin/getClientListWould list clients with filters, returning contact and profile data; getClient returns an individual record and addClient creates new ones.
Catalog
/admin/getEventListWould fetch the catalog of services (events) and service providers (units) configured for the company, including durations and pricing.
Availability
/admin/getStartTimeMatrixWould return available start times and open intervals for a service and provider so external apps can present real-time booking slots.
Use Cases
Sync bookings and clients into your data stack
- Pull bookings, statuses, and revenue from getBookings and getBookingRevenue into a warehouse or BI tool - Stream client records from getClientList into a CRM for marketing and retention - Reconcile services, providers, and pricing from getEventList and getUnitList across locations
Power custom booking experiences
- Surface real-time availability with getStartTimeMatrix and getAvailableTimeIntervals - Create, edit, and cancel appointments through book, editBook, and cancelBooking - Apply company-specific working hours and breaks via getWorkDaysInfo
Automate client communication workflows
- Detect new and changed bookings and trigger downstream SMS, email, or WhatsApp flows - Push appointment data to review-request and loyalty tools - Keep no-show and cancellation events in sync with retention automations
Centralize performance reporting
- Aggregate getBookingStats, getTopPerformers, and getTopServices across multiple companies - Track provider workload and utilization from getWorkload - Feed revenue and visitor metrics into executive dashboards
Connect via No-Code Tools
Automate this platform from the no-code stack you already use.
Technical Requirements
Authentication
Would require company login plus API key from the paid API Custom Feature, exchanged via getToken for a one-hour access token; user-level tokens for admin methods
Connectivity
Would build on JSON-RPC 2.0 over HTTPS against the login, public, and admin services on user-api.simplybook.me
Response format
JSON-RPC result objects normalized into consistent JSON for bookings, clients, services, providers, and availability
Rate limits
Adaptive throttling tuned to the company tenant, with token reuse within the one-hour validity window to avoid re-auth churn
Session management
Would need automatic token refresh on expiry, credential rotation, and re-login handling for the short-lived access token
Data freshness
Near real-time reads for bookings and availability, with optional scheduled syncs for clients and catalog data
Security
Encrypted credential vault, scoped tokens, and audit logging, aligned with SimplyBook.me's ISO 27001 and GDPR posture
Webhooks
Booking callback URLs (create, change, cancel) normalized into event-style notifications for downstream automation
Latency
Design target: sub-second reads on cached catalog and client data; multi-second writes when creating or editing bookings
Throughput
Design target: horizontally scaled workers sized to multi-location and multi-company booking volume
Reliability
Retry, backoff, and idempotency handling for book, editBook, and cancelBooking operations
Versioning
Clear versioning and change management would matter as SimplyBook.me evolves
Frequently asked questions
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 SimplyBook.me 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.