Aroundtime is built around explicit, scoped integrations.
Google Calendar
Read free/busy data, create events, and generate Google Meet links.
OIDC and SCIM
Authenticate and provision members for enterprise organizations.
Model Context Protocol
Let authorized AI clients read availability and schedule meetings.
REST API and webhooks
Use scoped API keys and signed, retried booking lifecycle events.
Embeds
Add inline or popup scheduling with vanilla JavaScript or React.
Security model
Integrations request only the scopes required for their job. Google login is separate from Calendar authorization. MCP clients receive user-approved read or write scopes. SCIM uses a per-connection bearer token.
REST API
Organization owners and admins create scoped API keys under Developer. Send the key as Authorization: Bearer atkey_… to /api/v1.
Available scopes independently grant read or write access to meeting types, availability, and bookings. The API supports meeting-type management, availability schedules, slot queries, booking creation, and booking lifecycle actions.
Webhooks
Webhook endpoints must use public HTTPS URLs. Aroundtime signs timestamp.payload with HMAC-SHA256 and sends:
X-Aroundtime-Signature: t={unix-seconds},v1={hex-signature}Failed deliveries retry with exponential backoff and remain in the durable D1 outbox. Supported events cover booking creation, rescheduling, cancellation, approval, rejection, and no-show.
Embeds
The @aroundtime/embed package provides inline and accessible popup modes. @aroundtime/embed/react exports thin React wrappers over the same messaging contract.
Embed configuration supports locale, light/dark theme, and name/email prefill. The iframe emits ready, height, and booking-completed messages after validating its parent/child origin.
Use the integration-specific pages for setup and operational details.