cal.com

Cal.com offers four developer-facing integration paths, each suited to a different level of control: a public API for building custom integrations, React scheduling components ("atoms") for embedding scheduling UI directly into a React app, OAuth clients for connecting your product to a user's Cal.com account, and a plain embed option for dropping Cal.com into an existing website. Which one you pick depends on whether you want to own the scheduling UI, just the data flow, or neither.

The four integration options at a glance

All four are documented under the Developer section of cal.com, alongside the API reference and component docs.

Building with the public API

The API is the most flexible option and the right starting point if your frontend isn't React, or if you need scheduling data to flow into your own system rather than render Cal.com's UI.

The general shape of the work:

1. Read the API documentation at the Developer → Documentation entry on cal.com to see the available endpoints and authentication requirements.
2. Authenticate your requests using the method the docs specify for your use case — note that OAuth is a separate, documented path (see below) if you're acting on behalf of other users.
3. Call the endpoints you need and handle responses in your own application logic.

Expected result: your application can create, read, or react to scheduling data without the user ever seeing a Cal.com interface. The specific endpoint list and auth details live in the docs, so treat those pages as the source of truth rather than guessing at paths.

Embedding scheduling UI with React atoms

If you're building a React app and want booking to feel like part of your product, Cal.com's scheduling components are the intended route. The site describes them as "react atoms" you use to add scheduling to your app — the idea being that you compose small scheduling primitives rather than iframing a whole booking page.

Use this when:

• Your app is already React.
• You want control over layout and styling around the scheduling step.
• You'd rather not maintain your own calendar and availability logic.

If your app isn't React, skip to the API or embed options instead — the atoms are React-specific by description.

Integrating via OAuth

OAuth is the option to reach for when your product needs to act on a Cal.com user's behalf — for example, a tool that reads their availability or creates bookings in their account after they grant permission.

The documented flow is "Create OAuth Client," which implies you register a client with Cal.com and then integrate using OAuth. Practically, that means:

1. Register your OAuth client through the developer resources on cal.com.
2. Implement the standard OAuth authorization flow in your app.
3. Use the granted access to call Cal.com on the user's behalf.

This is the right choice for multi-user products where each customer connects their own Cal.com account. It is not needed if you're only embedding a booking page for yourself.

Embedding Cal.com into a website

The simplest path: Cal.com provides an Embed resource specifically for putting Cal.com into your website. This suits marketing sites, landing pages, and any case where you just want visitors to book without building custom UI.

Choose embed over the API when you don't need the booking data inside your own application — you just need the booking to happen. Choose the API or atoms when the scheduling step has to be wired into your product's own state and logic.

How to decide

• Non-React app, need data in your system → Public API.
• React app, want native booking UI → Scheduling components (React atoms).
• Multi-user product acting on behalf of Cal.com accounts → OAuth client.
• Just need a booking form on a site → Embed.

These aren't mutually exclusive — a product could embed a booking page for end users while using the API server-side to sync confirmed meetings.

Common sticking points

• Confusing OAuth with API keys. OAuth is for acting on behalf of other users; if you only need your own account's data, you likely don't need the OAuth client flow.
• Reaching for atoms in a non-React codebase. The components are React-based; other stacks should use the API or embed.
• Assuming embed gives you the data. Embedding puts the booking UI on your page, but pulling that booking into your own database is an API concern.
• Skipping the docs. Endpoint names, scopes, and component props change; the Developer → Documentation and Scheduling Components pages on cal.com are the authoritative references.

Start with the docs page that matches your stack, confirm the authentication model before writing integration code, and pick the lightest option that still gets scheduling data where you need it.

Cal.ai is Cal.com's AI-powered scheduling feature, described on the Cal.com site as "supercharged scheduling with AI-powered calls." It sits alongside the core Cal.com scheduling app rather than replacing it: you still use Cal.com to define your availability and event types, and Cal.ai adds an AI layer that handles calls as part of the booking flow. The homepage presents it as something you can try immediately ("Try Cal.ai now!"), so the practical way to evaluate it is to treat it as an add-on to an existing Cal.com setup.

Where Cal.ai sits in the Cal.com product

Cal.com's own description of itself is "a fully customizable scheduling software for individuals, businesses taking calls and developers building scheduling platforms where users meet users." The homepage groups its offerings into a few buckets:

Cal.ai appears in the same navigation list as Payments, Workflows, and Webhooks — that is, as one capability within the platform, not a separate product with its own signup. The homepage also shows a standard booking card (a "Partnerships Meeting" with 15m/30m/45m/1h options, Cal Video, and a Europe/Amsterdam timezone calendar), which is the ordinary Cal.com booking experience that Cal.ai is meant to enhance.

What "AI-powered calls" implies for scheduling

The phrase "AI-powered calls" is the only functional detail the source material gives. Read literally, it points to voice or call handling being part of the scheduling process — for example, an AI agent that talks to a caller and lands the meeting on a calendar. The site does not specify:

• which languages or regions the calls support
• whether the AI joins an existing meeting or places outbound calls
• how it connects to specific event types
• what happens when the AI can't resolve a request

Because those details aren't in the page evidence, don't assume them. If you need them, check the Cal.ai page and the help docs linked from the site before committing a workflow to it.

Who it's aimed at

The site's audience framing is broad — individuals, teams, organizations, and enterprises — plus developers building scheduling into their own products. Cal.ai is most plausibly relevant if your bottleneck is the conversation before the booking (qualifying a lead, answering routine questions, routing to the right person) rather than the calendar mechanics themselves. If your bookings already happen through a link with no human conversation, Cal.ai may add little.

How to evaluate it in practice

1. Start from a working Cal.com setup. Define at least one event type with duration options and a connected calendar, since Cal.ai is described as enhancing scheduling rather than standing alone.
2. Open the Cal.ai entry point from the Cal.com navigation and see what it asks you to configure.
3. Check the help docs for setup steps and limitations before wiring it into a customer-facing flow.
4. Test with a low-stakes event type — for example, an internal "intro call" — so a misrouted or mishandled call doesn't affect real prospects.
5. Verify the outcome in your calendar, not just in the Cal.ai interface, to confirm the booking landed where you expect.

Practical caveats

• The homepage says "No credit card required" for signing up, but that statement is attached to the general signup, not specifically to Cal.ai. Pricing for Cal.ai isn't stated in the source material — check the pricing page rather than assuming it's included.
• "Try Cal.ai now!" is a call to action, not a description of scope. Treat the feature list as unverified until you read the dedicated page.
• If you're a developer, note that the documented integration paths on the homepage are the public API, React scheduling components, and OAuth — Cal.ai isn't listed as a developer integration surface there.

Bottom line: Cal.ai is Cal.com's AI layer for the calling side of scheduling, offered within the same platform as its booking, payments, and workflow tools. It's worth a look if pre-booking conversations are your constraint; confirm the specifics on the Cal.ai and pricing pages before you build a process around it.

Cal.com is a customizable scheduling platform that lets other people book time with you through a link, an embed, or an app, instead of going back and forth over email. It is built for three broad audiences: individuals who want simple personal scheduling, teams and organizations that need collaborative or controlled scheduling, and developers who want to add scheduling into their own products. You can start with Google or email sign-up, and the site states no credit card is required to get started.

What problem it solves

The core job is turning "when are you free?" into a bookable page. You define the event, the available durations, and your availability; the other person picks a slot. The homepage example shows this directly: a "Partnerships Meeting" event with 15m, 30m, 45m, and 1h options, a Cal Video conferencing location, and a calendar rendered in a specific time zone (Europe/Amsterdam). That combination — event type, duration choices, conferencing, and time-zone-aware calendar — is the basic unit of the product.

Who it is for

Cal.com organizes its offering by team size and by use case, which is a useful way to decide whether it fits you.

Use-case pages listed on the site include Recruiting, Sales, HR, Education, Support, Healthcare, Telehealth, and Marketing. If your scheduling need resembles one of those, that page is the fastest way to judge fit.

Main capabilities

• Bookable event links — share a link so others can pick a time, with configurable durations.
• Collective events — schedule events with multiple participants.
• Dynamic group links — book meetings with multiple people.
• Instant meetings — meet with clients in minutes.
• Out of office — schedule time off.
• Payments — accept payments for bookings.
• Workflows — automate scheduling and reminders.
• Webhooks — get notified when something happens.
• Embed — put Cal.com into your website.
• App Store — integrate with other apps.
• Cal.ai — described as "supercharged scheduling with AI-powered calls."

For developers

Cal.com exposes several building blocks rather than only an end-user app:

• Documentation for the platform.
• Public API to build your own integrations.
• Scheduling components — React atoms to add scheduling to your app.
• OAuth client to integrate Cal.com using OAuth.

This matters if you are building a product where users meet users and want scheduling inside it rather than sending people to a separate site.

How to decide

Choose Cal.com if you want a scheduling layer you can customize and, if needed, embed or build on through an API. It fits individuals who just need a booking link, teams that need shared or multi-participant scheduling, and developers who want scheduling as a component. If you only need a single static booking page with no integration or customization, the extra developer surface is optional rather than required — you can use the individual scheduling path.

Pricing and plan limits are not covered in the material here; check the Pricing page for current terms before committing.

Cal.com is a customizable scheduling app for individuals, teams, organizations, and enterprises, and it also exposes developer tools for building scheduling into other products. Its core feature set covers booking pages with selectable meeting lengths, collective and group scheduling, instant meetings, payments, automated workflows and reminders, out-of-office time, and webhooks. The features below are the ones named on Cal.com's own site; exact plan availability and limits are not specified there, so check the pricing page before assuming a feature is included in your tier.

Booking pages and meeting lengths

The homepage shows a live booking example: a "Partnerships Meeting" with selectable durations of 15m, 30m, 45m, and 1h, a video location (Cal Video), and a timezone (Europe/Amsterdam) displayed alongside a monthly calendar.

That illustrates the basic unit of Cal.com: a bookable event type where the host defines duration options, the conferencing location, and availability, and the guest picks a slot. The site describes this as "personal scheduling made simple" for individuals and "collaborative scheduling for groups" for teams.

Scheduling formats beyond one-to-one

Cal.com lists several distinct ways to structure a meeting:

The distinction matters when choosing: collective events suit panels or interviews where several hosts must all attend, while dynamic group links route a booker to an available member of a group rather than requiring one specific person.

Payments, workflows, and notifications

• Payments — accept payments for bookings, so a paid consultation can be collected as part of the booking flow rather than invoiced separately.
• Workflows — automate scheduling and reminders, which is the mechanism for confirmation emails, follow-ups, and reducing no-shows.
• Webhooks — get notified when something happens, useful for triggering actions in your own systems when a booking is created or changed.

Embedding and integrations

Cal.com can be embedded into your website, and the site points to an App Store for integrating with other apps. For teams already running a CRM or calendar stack, the embed plus app integrations are the practical path to avoiding double-entry.

Developer and AI options

For developers, Cal.com documents:

• Public API — build your own integrations
• Scheduling Components — React atoms to add scheduling to your app
• OAuth client — integrate Cal.com using OAuth
• Cal.ai — described as "supercharged scheduling with AI-powered calls"

If you are building scheduling into a product rather than just booking your own meetings, these are the relevant entry points; the API and component docs are the place to confirm current capabilities.

Choosing based on your situation

• Solo professional — a booking page with a few duration options and reminders covers most needs.
• Team or organization — look at collective events, dynamic group links, and the team/organization tiers, which the site frames around collaboration and, at the organization level, more control and security.
• Enterprise — the site advertises enterprise-level scheduling solutions, but the specific controls are not detailed on the homepage.
• Developer — start with the API, React components, or OAuth depending on whether you are integrating, embedding, or building a full scheduling surface.

Sign-up is offered via Google or email, and the homepage states no credit card is required to get started. Pricing, per-seat limits, and which features sit behind paid tiers are not covered in the material here — check cal.com/pricing for that.

Cal.com is designed for four broad groups: individuals who need simple personal scheduling, teams that coordinate availability across people, organizations and enterprises that need more control and security, and developers who want to build scheduling into their own products. The right fit depends on which of those describes you — the same platform serves all four, but the features you rely on differ.

Individuals: personal scheduling made simple

If you're a freelancer, consultant, or anyone who books one-to-one meetings, Cal.com's individual use case is "personal scheduling made simple." You publish your availability, share a link, and let people pick a slot instead of trading messages.

The homepage example shows what this looks like in practice: a "Partnerships Meeting" event with selectable durations of 15m, 30m, 45m, or 1h, a Cal Video location, and a timezone (Europe/Amsterdam) with a monthly calendar. That single event page replaces the back-and-forth of proposing times.

You're likely a good fit if:

• You book meetings with people outside your organization.
• You want bookers to choose from your real availability.
• You don't need shared team calendars or admin controls.

Teams: collaborative scheduling for groups

For teams, Cal.com positions itself as "collaborative scheduling for groups." The relevant capability here is Collective Events — "schedule events with multiple participants." Instead of one person's calendar, the booking logic accounts for several people's availability.

This matters when a meeting requires more than one person from your side, such as a sales call with an account executive and a solutions engineer, or a panel-style session. The team use case is about coordinating availability rather than just publishing one calendar.

Organizations and enterprises: more control and security

Cal.com separates these two tiers explicitly:

Both are aimed at scale, but the organization tier is framed around larger teams needing more control and security, while the enterprise tier is a distinct offering for enterprise-level requirements. If you're evaluating for a large company, the enterprise page is the relevant starting point rather than the individual or team descriptions.

Developers: building scheduling into your own product

Cal.com is also a platform, not just an app. The developer resources listed on the site include:

• Documentation — "documentation for the Cal.com platform."
• API — "build your own integrations with our public API."
• Scheduling Components — "use our react atoms to add scheduling to your app."
• OAuth — "integrate Cal.com using OAuth."
• Webhooks — "get notified when something happens."

The site's own framing is that Cal.com serves "developers building scheduling platforms where users meet users." So if your goal is to embed scheduling inside your own product rather than just book your own meetings, this is the intended path.

Use cases that cut across all four groups

Cal.com lists use cases that apply regardless of which group you fall into: Recruiting, Sales, HR, Education, Support, Healthcare, Telehealth, and Marketing. Alongside these are feature-level tools such as:

• Embed — put Cal.com into your website.
• Out of Office — schedule time off.
• Payments — accept payments for bookings.
• Workflows — automate scheduling and reminders.
• Instant Meetings — meet with clients in minutes.
• Dynamic Group Links — book meetings with multiple people.

If your need maps to one of these use cases, that's a stronger signal than the individual/team/organization/enterprise label alone.

How to decide

Ask one question first: are you booking your own meetings, coordinating other people's, running scheduling at organizational scale, or building scheduling into software?

• Your own meetings → individual scheduling.
• Multiple participants on your side → team / Collective Events.
• Control and security at scale → Organizations or Enterprise.
• Scheduling inside your product → API, OAuth, and Scheduling Components.

One practical note: the signup options shown are "Sign up with Google" and "Sign up with email," with "No credit card required" stated for getting started. Pricing details are not covered in the material here — check the pricing page directly before committing to a tier.