Apointoo SDK, the headless, API-first foundation
The first SDK release: an adapter-pluggable core, the first booking adapter, and PII-safe attribution capture.
What shipped
The first public release of the Apointoo SDK set the shape of everything that followed.
An adapter-pluggable core
Every external dependency, booking system, notification channel, storage, sits behind an interface. Swapping Boulevard for a calendar, or Brevo for another email provider, means swapping an adapter, not rewriting the system. That decision is what let later releases add WhatsApp, calendars, and conversion reporting without touching the core.
The first booking adapter
The Boulevard (BLVD) booking adapter shipped with slot-leak compensation from the start, if a slot escapes between the read and the confirm, the system reacts instead of double-selling.
Attribution from day one
Attribution capture (gclid, fbclid, msclkid) has been in the SDK since v0.1.0, with PII-free logging. Knowing which click brought which booking wasn't a feature added later, it was the premise. The whole path to offline conversion reporting starts here.