v2 REST endpoints returning 404 for personal workspace API key

[arielskeren]

I’m integrating Cal.com v2 endpoints into my app using the personal workspace API key (cal_…). The goal is to manage bookings and event types via the new REST API endpoints. Per the documentation, I’m calling:

• GET /v2/bookings
• GET /v2/event-types
• GET /v2/users/{userId}/bookings
• GET /v2/slots/...
• However each request returns:

{
"status": "error",
"error": {
"code": "NotFoundException",
"message": "Cannot GET /v2/bookings?..."
}
}

I’ve confirmed the requests include the Authorization: Bearer header and (when needed) the cal-api-version: 2024-09-04 header. Removing the key gives a 403 (“Forbidden”), so the API does see the request—it just can’t find the route when the key is present.

Do the /v2/event-types, /v2/bookings, and related endpoints require a specific plan (Platform or Managed) or OAuth flow? Are they available to personal accounts using standard API keys?

If yes, what base path / access token should we use? e.g., do we need team-based endpoints (/v2/teams/{teamId}/…) or organization-style endpoints (/v2/organizations/{orgId}/…), and how do we obtain the correct team/org identifiers for a personal workspace?

If v2 requires OAuth/managed-user tokens, what is the recommended approach to obtain them for a single-user workspace so we can migrate off the v1 API?

Thanks!

[Pranav-0440]

Hi @arielskeren 👋
I looked into this — the 404 errors are expected for personal workspace API keys.

The new v2 REST API currently supports Platform and Managed workspaces, not personal ones. That’s why your /v2/bookings and /v2/event-types calls return NotFoundException even though the Bearer key is valid.

For personal workspaces, you can still use the v1 API (/api/bookings, /api/event-types) until Cal.com extends v2 support to standalone accounts.

🔧 Workaround Options:

Use an OAuth app or Managed API key from a team workspace (accessible under Settings → API Keys).

Or switch to /v1/ endpoints for personal use — same data, just legacy routes.

📘 Reference:
Cal.com Docs → https://docs.cal.com/api

The v2 endpoints listed there are scoped to managed/team environments only.

Hope this helps clarify why the routes are returning 404 🙌
— Pranav Ghorpade (@Pranav-0440)