2 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
This article introduces the new API key feature that lets users create and manage keys for accessing your application's API. It covers key functionalities like instant revocation, user and organization scoping, and programmatic management through the Backend SDK. Pricing will be usage-based after the beta period.
If you do, here's more
Clerk has launched a public beta for API keys, allowing users to create keys that grant access to an application’s API on their behalf. This feature is integrated into prebuilt UI components for user and organization profiles. Once enabled in the Clerk Dashboard, an API Keys tab appears, enabling users to manage their keys easily. There’s also a standalone `<APIKeys />` component that developers can use anywhere in their application.
The backend SDK allows for programmatic creation and management of API keys, giving developers control over scopes, claims, and expiration settings. API keys are designed to maintain context tied to specific users or organizations. They feature instant revocation through opaque tokens, which can be invalidated immediately. Users can define access scopes, add custom claims for additional metadata, and choose between setting a time-to-live or keeping keys long-lived.
During the beta phase, API keys are free to use. Once the feature moves to general availability, a usage-based pricing model will take effect, charging $0.001 per key creation and $0.00001 per verification. Clerk plans to notify users at least 30 days before billing starts and will provide detailed usage stats in the Dashboard.
Resources for getting started include a comprehensive API keys guide, a backend SDK reference, a tutorial for building a SaaS application with Clerk, and a way to enable API keys in the Dashboard. Clerk invites user feedback during the beta phase to help refine the feature, encouraging users to reach out through their feedback portal or Discord community for support and suggestions.
Questions about this article
No questions yet.