Project setup

1. Clone / copy source into your project root:

   cp -r source/ ./calcom
   

   Or set source/ as your project root if adopting the full monorepo.

2. Install dependencies from the workspace root:

   corepack enable
   yarn install
   

3. Configure environment variables. Copy .env.example to .env in apps/web and apps/api/v2:

   cp apps/web/.env.example apps/web/.env
   cp apps/api/v2/.env.example apps/api/v2/.env
   

   Minimum required vars:

   DATABASE_URL=postgresql://user:pass@localhost:5432/calcom
   NEXTAUTH_SECRET=<random-32-char-string>
   NEXTAUTH_URL=http://localhost:3000
   NEXT_PUBLIC_WEBAPP_URL=http://localhost:3000
   

4. Run database migrations:

   cd packages/prisma && npx prisma migrate deploy
   

5. Wire tsconfig paths if consuming packages directly in a TypeScript host project. Add to your tsconfig.json:

   {
     "compilerOptions": {
       "paths": {
         "@calcom/*": ["./calcom/packages/*/src"]
       }
     }
   }
   

6. Start the platform locally:

   yarn dev
   

   • Web app: http://localhost:3000
   • API v1 proxy: http://localhost:3002
   • API v2 (NestJS): http://localhost:3004

Public API

sha256Hash

import { sha256Hash } from "./apps/api/v2/src/lib/api-key";

function sha256Hash(token: string): string;

Hashes an API key token with SHA-256. Use this when storing or comparing API keys server-side — never store raw tokens. Input is any string; output is a lowercase hex digest.

isApiKey

import { isApiKey } from "./apps/api/v2/src/lib/api-key";

function isApiKey(authString: string, prefix: string): boolean;

Returns true if authString starts with the given prefix (defaults to "cal_"). Use this in auth middleware to distinguish Cal API keys from OAuth bearer tokens before attempting to hash and look up the key.

stripApiKey

import { stripApiKey } from "./apps/api/v2/src/lib/api-key";

function stripApiKey(apiKey: string, prefix?: string): string;

Removes the "cal_" prefix (or a custom prefix) from an API key string. Use this to extract the raw token before hashing, so storage is consistent regardless of whether callers include the prefix.

NestServer (singleton)

// apps/api/v2/src/main.ts
class NestServer {
  public static async getInstance(): Promise<Express>;
}

Singleton that boots the NestJS application once per container lifecycle, runs the bootstrap() configuration (pipes, interceptors, CORS), and returns the underlying Express instance. Use getInstance() to embed the NestJS API inside a Vercel serverless function or an existing Express server.

Working examples

Scenario - Validate and hash an incoming API key in Express middleware

An Express gateway needs to authenticate requests using Cal API keys before proxying to downstream services.

import express, { Request, Response, NextFunction } from "express";
import { isApiKey, stripApiKey, sha256Hash } from "./calcom/apps/api/v2/src/lib/api-key";

const app = express();

async function apiKeyAuth(req: Request, res: Response, next: NextFunction) {
  const authHeader = req.headers.authorization ?? "";
  const token = authHeader.replace(/^Bearer\s+/, "");

  if (!isApiKey(token, "cal_")) {
    return res.status(401).json({ error: "Not a Cal API key" });
  }

  const rawToken = stripApiKey(token, "cal_");
  const hashed = sha256Hash(rawToken);

  // Compare hashed against your DB record
  // const stored = await db.apiKey.findUnique({ where: { hashedKey: hashed } });
  // if (!stored) return res.status(403).json({ error: "Invalid key" });

  console.log("Hashed key for lookup:", hashed);
  next();
}

app.use("/api", apiKeyAuth, (req, res) => {
  res.json({ message: "Authenticated" });
});

app.listen(4000);

Scenario - Embed the NestJS API v2 inside a Vercel serverless function

Mount the Cal NestJS app as a Vercel handler without running a separate process.

// api/calcom.ts  (Vercel edge/serverless file)
import type { VercelRequest, VercelResponse } from "@vercel/node";
// NestServer is the singleton exported from main.ts logic
// Replicate its pattern directly:
import "dotenv/config";
import { NestFactory } from "@nestjs/core";
import type { NestExpressApplication } from "@nestjs/platform-express";
import type { Express } from "express";
import { AppModule } from "../calcom/apps/api/v2/src/app.module";
import { bootstrap } from "../calcom/apps/api/v2/src/bootstrap";

let server: Express;

async function getServer(): Promise<Express> {
  if (!server) {
    const app = await NestFactory.create<NestExpressApplication>(AppModule, { bufferLogs: true });
    bootstrap(app);
    await app.init();
    server = app.getHttpAdapter().getInstance();
  }
  return server;
}

export default async function handler(req: VercelRequest, res: VercelResponse) {
  const expressApp = await getServer();
  expressApp(req as any, res as any);
}

Scenario - Run the API proxy locally to fan out v1 / v2 traffic

Spin up the connect-based proxy that routes /v2 to NestJS and everything else to the legacy v1 API.

// proxy.js
const http = require("node:http");
const connect = require("connect");
const { createProxyMiddleware } = require("http-proxy-middleware");

const apiProxyV1 = createProxyMiddleware({ target: "http://localhost:3003" });
const apiProxyV2 = createProxyMiddleware({ target: "http://localhost:3004" });

const app = connect();
app.use("/v2", apiProxyV2);  // must be registered before the catch-all
app.use("/", apiProxyV1);

http.createServer(app).listen(3002, () => {
  console.log("API proxy listening on :3002");
});

Run with node proxy.js. Matches the logic in apps/api/index.js exactly.

File walkthrough

• apps/ - Contains all deployable apps: web (Next.js booking UI), api (connect proxy + NestJS v2 REST API).
• apps/api/index.js - Lightweight connect server that proxies /v2 to NestJS on :3004 and everything else to the v1 handler on :3003.
• apps/api/v2/src/main.ts - NestJS application entry point; defines the NestServer singleton and local-dev startup path.
• apps/api/v2/src/lib/api-key/index.ts - Pure utility functions for API key hashing, prefix detection, and stripping.
• apps/api/v2/src/modules/auth/guards/or-guard/index.ts - Re-exports the Or guard for composing multiple NestJS auth guards.
• apps/api/v2/src/platform/event-types/event-types_2024_06_14/transformed/index.ts - Re-exports event-type transformation helpers for the 2024-06-14 API version.
• packages/ - Shared workspace packages: Prisma schema, UI components, tRPC routers, config helpers, i18n.
• docker-compose.yml - Defines Postgres and the web/api services for local container-based development.
• turbo.json - Turborepo task graph; defines build, dev, lint, test pipelines with caching.
• biome.json - Biome linter/formatter rules applied across the monorepo in lieu of ESLint + Prettier.

Common pitfalls and fixes

• Wrong package manager: Running npm install instead of yarn install breaks Yarn Berry workspace resolution. Fix: corepack enable && yarn install.
• Missing DATABASE_URL: Prisma throws a cryptic engine error at startup. Fix: ensure DATABASE_URL is set in every app's .env before running migrations or starting the server.
• NEXTAUTH_SECRET not set in production: NextAuth silently falls back to an insecure value. Fix: always set a strong random value; generate with openssl rand -hex 32.
• NestJS bootstrap not called before app.init(): CORS, global pipes, and validation decorators will be absent. Fix: always call bootstrap(app) before await app.init() as shown in main.ts.
• ESM/CJS interop with connect and http-proxy-middleware: Using import syntax in the proxy file causes a runtime error because connect is CJS. Fix: keep apps/api/index.js as a .js CommonJS file or add "type": "commonjs" to that package's package.json.
• Turborepo cache stale after schema changes: Cached builds may not include new Prisma client types. Fix: run turbo run build --force or clear .turbo/ after any schema.prisma edit.

Vibe-coding prompt template

I have a copy of the Cal.diy open-source scheduling monorepo (upstream package: user@example.com)
in the `source/` directory of this project. I also have a USAGE.md that documents the real exports
and file layout.

Please help me integrate Cal.diy into my existing Node.js / TypeScript project by doing the following
steps one at a time, confirming with me after each:

1. Read USAGE.md and source/apps/api/v2/src/lib/api-key/index.ts to understand the API key utilities.
2. Add the required npm dependencies listed in USAGE.md to my package.json.
3. Create an Express middleware file that uses `isApiKey`, `stripApiKey`, and `sha256Hash` from
   source/apps/api/v2/src/lib/api-key/index.ts to authenticate requests.
4. Wire the NestJS API v2 (source/apps/api/v2/src/main.ts bootstrap pattern) into my existing
   Express app as a sub-router under /calcom.
5. Set up the required environment variables (DATABASE_URL, NEXTAUTH_SECRET, NEXTAUTH_URL) in my
   .env file.
6. Confirm the proxy routing logic from source/apps/api/index.js and replicate it if I need
   separate v1/v2 routing.

Use only the real exports visible in USAGE.md. Do not invent function names or module paths.

License and credit

Cal.diy is released under the MIT License (see source/LICENSE). It is a community fork of Cal.com with enterprise features removed. Upstream repository: https://github.com/calcom/cal.diy. Upstream npm package identifier: user@example.com.

This product’s unique contribution is clean room implementation of valuable code block into AVCP compatible standard.

完整安装指南与集成提示词将在购买后解锁。

Resource Scheduling Table (Drag & Assign)

CRM, ERP, Admin & Internal Tools

US$7