From 3b8b2299af387d7c66e391429d4955df32f30d3b Mon Sep 17 00:00:00 2001 From: Lauris Skraucis Date: Thu, 22 Jan 2026 08:36:57 +0000 Subject: [PATCH] docs: OAuth self serve (#27090) --- docs/api-reference/v2/oauth.mdx | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/api-reference/v2/oauth.mdx b/docs/api-reference/v2/oauth.mdx index 491780c380..7a79d638e0 100644 --- a/docs/api-reference/v2/oauth.mdx +++ b/docs/api-reference/v2/oauth.mdx @@ -22,9 +22,11 @@ As an example, you can view our OAuth flow in action on Zapier. Try to connect y ### OAuth Client Credentials -Only the Cal.com team can create new OAuth clients. Please fill out [this form](https://i.cal.com/forms/4052adda-bc79-4a8d-9f63-5bc3bead4cd3) and book us to get started. +You can create an OAuth client via the following page https://app.cal.com/settings/developer/oauth. The OAuth client will be in a "pending" state +and not yet ready to use. -The Cal.com team will register the app and provide you with the Client ID and Client Secret. Keep these credentials confidential and secure. +An admin from Cal.com will then review your OAuth client and you will receive an email if it was accepted or rejected. If it was accepted then your OAuth client +is ready to be used. ### Authorization URL @@ -88,4 +90,4 @@ To verify the correct setup and functionality of OAuth credentials you can use t Headers: -- Authorization: Bearer _exampleAccessToken_ \ No newline at end of file +- Authorization: Bearer _exampleAccessToken_