API Routes Returning 404 Errors - Cannot Access Any Endpoints

[BeclaAR]

Hi!

Issue Description

I am experiencing persistent 404 errors when trying to access various API routes in the Cal.com platform API (v2), despite the API service starting normally. This issue affects all routes tested, suggesting a configuration or routing problem rather than specific endpoint failures.

Technical Environment

• Cal.com API Version: v2
• Node.js: Latest
• Package Manager: yarn
• Tech Stack:
  • TypeScript 5.7.2
  • React 18.2.0
  • Next.js 15.3.0
• API Start Command:

  cd apps/api/v2/ && yarn workspace @calcom/api-v2 build && yarn workspace @calcom/api-v2 start

Error Details

Routes Tested (All Returning 404):

• GET /
• GET /v2
• GET /api//v2
• GET /api/users
• GET /v2/users

Sample Error Logs:

{ "error": "Http Exception Filter: Cannot GET /api/users", "context": "HttpExceptionFilter", "service": "cal-platform-api", "exception": { "message": "Cannot GET /api/users", "name": "NotFoundException", "response": { "error": "Not Found", "message": "Cannot GET /api/users", "statusCode": 404 }, "status": 404 }, "method": "GET", "url": "/api/users", "timestamp": "2025-07-22 10:24:16.060" }

Additional Issue: API Key Generation Problem

Critical Issue: After purchasing a license key, I am unable to create API keys through the Cal.com interface. This prevents proper API authentication and testing.

Expected Behavior

• API routes should respond with appropriate data or status codes
• API key generation should work with purchased license
• Routes like /api/users and /v2/users should be accessible

Troubleshooting Steps Taken

1. ✅ Verified API service starts successfully
2. ✅ Confirmed routes are being accessed correctly
3. ✅ Checked for obvious configuration issues
4. ✅ Tested multiple endpoints
5. ✅ Verified build process completes without errors

Questions for Support

1. Are there known compatibility issues with the current tech stack?
2. What are common causes of universal 404 errors in Cal.com API v2?
3. Why might API key generation fail after purchasing a license?
4. Are there additional configuration steps required for API v2 routing?

Request for Assistance

Could you please provide guidance on:

• Configuration steps to resolve routing issues
• API key generation troubleshooting
• Debugging steps to identify the root cause

Any help would be greatly appreciated. Please let me know if additional information about the setup is needed.

Best regards, Becla

[dosubot[bot]]

Hi @BeclaAR! I'm Dosu and I’m helping the cal.com team.

The most common cause of universal 404 errors in Cal.com API v2 is misconfiguration of critical environment variables, especially the license key. Make sure your CALCOM_LICENSE_KEY environment variable exactly matches the value in the deployments table of your database. Both must be set for the API to function—if they don’t match, all endpoints will return 404s, and features like API key generation will fail, even if the UI shows a valid license. See this discussion for details.

Check your .env file for these key variables:

• CALCOM_LICENSE_KEY (must match DB)
• REWRITE_API_V2_PREFIX (set to "1" to rewrite /api/v2 to /v2)
• API_KEY_PREFIX (usually cal_)
• GET_LICENSE_KEY_URL (should be a valid Cal.com license endpoint, e.g., https://goblin.cal.com/v1/license or https://console.cal.com/api/license—see this issue)

After updating your environment variables, restart the API service. You can verify available endpoints and routing by visiting /docs (Swagger UI) if enabled.

For API key generation: it depends on the license key being valid and recognized by both the environment and the database. If you still can’t generate API keys after fixing the license key, double-check that your user has the necessary permissions and that there are no feature flags or organization settings disabling API access. The API key creation logic is handled by the backend and requires a valid license context—misconfiguration here will block key creation even if the UI appears correct (source).

If you’re using subdomains or custom domains, make sure to set RESERVED_SUBDOMAINS as needed (reference).

Recent changes to API v2 routing and dependency injection have been merged and tested, so if you’re on the latest version and your environment is correct, the API should be accessible (recent PR).

If you’re still seeing 404s after these steps, check your logs for any startup errors or warnings about missing environment variables, and confirm that your build process is using the correct .env file. You can also inspect the Swagger docs at /docs to see which endpoints are actually registered and available.

Let me know if you need more specific debugging steps or want to share your current environment variable setup for review.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[BeclaAR]

Hi @dosu, thanks for the detailed explanation!

In my case, the license key is not automatically written to the database. Even when I manually insert the license key into the deployments table, the issue persists and I still get 404 errors.
I’ve double-checked all the other environment variables you mentioned—they are set correctly.

Does anyone have any other ideas what might be causing this?

Thanks in advance!

[dosubot[bot]]

Based on the code and recent issues, universal 404s in Cal.com API v2 almost always point to a routing or environment misconfiguration—not license validation. Even if the license is missing or invalid, the API should return 401s, not 404s, and routes should still be registered unless something blocks them at the framework level (source).

Here are the most likely causes and next steps:

• Double-check the global prefix and REWRITE_API_V2_PREFIX. If REWRITE_API_V2_PREFIX is set to "1", /api/v2 is rewritten to /v2. Try both /api/v2/users and /v2/users to see if either works (source).
• Make sure your .env file is actually being loaded by the process. Sometimes, running the API directly (not via the root workspace) can cause it to miss the correct .env file.
• Confirm that NODE_ENV is set as expected and matches your intended environment.
• Check the Swagger UI at /docs (if enabled) to see which routes are actually registered. If /docs is missing, it’s a sign the app didn’t bootstrap routes at all.
• Review your startup logs for any warnings or errors about route registration, missing modules, or failed middleware.
• If you’re using a custom domain or subdomain, ensure RESERVED_SUBDOMAINS is set correctly (source).
• For license validation, make sure GET_LICENSE_KEY_URL is set to a valid endpoint like https://goblin.cal.com/v1/license—some users fixed 404s by updating this (source).

If all else fails, try running a clean build and restart the API service after confirming all environment variables and .env files are correct. If you can share your startup logs or .env (with secrets redacted), I can help spot any subtle issues.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}