The API's resources are calendars, events, access rules, settings, colors, free/busy and notification channels. There's no resource for appointment schedules, Google's booking pages. You set those up by hand in Calendar, and the bookings they take arrive as ordinary events, which your sync can read like any other.
Calendar also handles its own reminders and booking confirmations, so there's no reason to rebuild those. What it can't do is tell your job system, CRM or billing that a booking exists. n-frames builds that connection: the watch channels, the sync tokens, the renewals, and the mapping from a calendar event to a job, a visit or an invoice. Where a business runs many booking pages, we can also set them up through browser automation, because the API has no endpoint for it.