OAuth Clients, Now Self-Serve
Registering an OAuth application against Cal.com used to be an internal-ticket problem. It shouldn't be. Today we're shipping self-serve OAuth client management so platform teams can move at their own pace.
If you're building a scheduling experience on top of Cal.com, the first thing you need is an OAuth client. Historically that meant a support ticket, a Slack thread, or a coordinated deploy on our side. For a platform primitive that sits at the very start of every integration, that friction was the wrong default.
So we made it self-serve. You can now register and manage OAuth applications that integrate with Cal.com directly from settings Manage OAuth Clients.
Why this belongs in the product
OAuth client credentials are not a one-time artifact. They get rotated when someone leaves the team. They get scoped down when a security review lands. They get spun up fresh for a staging environment that didn't exist last quarter. Any workflow that requires a human on our side to unblock those events is a workflow that eventually blocks a launch.
Pushing client management into the dashboard means the team that owns the integration also owns its lifecycle — creation, rotation, and cleanup — without waiting on us.
What it unlocks
The obvious win is speed: a developer evaluating Cal.com on a Tuesday afternoon can register a client, wire up a redirect URI, and have a working OAuth flow before the coffee gets cold. The less obvious win is hygiene. When creating a client is cheap, teams stop sharing one "prod" credential across three environments. Staging gets its own client. The abandoned prototype gets deleted instead of lingering with valid tokens.
We kept the surface area intentionally small for this first pass — register, view, manage Manage OAuth Clients. The paired help-center article walks through the exact fields; this post is just the why.
What's next
Self-serve registration is the foundation. On top of it we want to build the things that actually make OAuth pleasant at scale: finer-grained scopes, per-client audit trails, and clearer separation between test and production credentials. If you're integrating with Cal.com and have opinions about what should come next, we'd like to hear them before we build it.