SimplyBook.me API
SimplyBook.me publishes a public developer API on JSON-RPC 2.0, covering public booking methods plus admin CRUD on bookings, clients, services, and providers. Auth exchanges a personal API key for a one-hour token via getToken. Docs are public with JS and PHP client examples.
Frequently asked questions
SimplyBook.me scores C on the API Report Card. SimplyBook.me publishes a public developer API on JSON-RPC 2.0, covering public booking methods plus admin CRUD on bookings, clients, services, and providers. Auth exchanges a personal API key for a one-hour token via getToken. Docs are public with JS and PHP client examples.
SimplyBook.me has an official API, but teams routinely hit its limits: gated access, partial coverage, or paid tiers. Most end up supplementing it with exports or an unofficial API layer like Supergood.
SimplyBook.me is a cloud-based online appointment scheduling and booking platform that lets service-based businesses accept reservations 24/7 across multiple channels (website widget, Facebook, Instagram, Google Maps, ClassPass, and the Booking.page marketplace).
Vertical: misc (Appointment Scheduling / Online Booking / SMB SaaS). A solo practitioner or small shop signs up, configures services, providers, working hours, and a booking widget; embeds it on their site or shares a Booking.page URL; toggles ~60 optional 'Custom Features' (HIPAA mode, intake forms, deposits, memberships, gift cards, coupons, recurring bookings, group classes, SOAP notes, etc.); connects Google/Outlook calendar, Stripe/PayPal, and SMS credits; clients self-book and pay; staff manage the day from the admin console or branded iOS/Android apps.
Moderate.
HQ: Cyprus (offices in Iceland and Ukraine). Founded: 2009/2011 (parent Notando Ltd., 2001). Owner: team.blue (acquired 2023). Employees: ~40-52. Customers: 10,000+ paying / 50,000+ businesses cited.
Founded as Notando in Iceland in 2001; SimplyBook.me product launched ~2009 and rebranded in 2011. Acquired by team.blue in 2023.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.