Manage your environment keys. Choose the correct architectural pipeline for your deployment framework below.
Verify your email: Your production API keys are ready to use but remain securely locked until you verify your email using the verification link sent to your registered email address.
Synchronizing with edge router...
Designed exclusively for private, secure server environments.
For security, existing API keys are hidden and cannot be viewed again. Roll the key to generate a new one. After generating new keys, update them in your application or backend immediately and store them securely. Never share your API keys.
Test your keys in the 'Interactive Sandbox' to verify functionality before integrating them into your site.
Site Builders & Frontend Developers: If your integration runs in a frontend environment such as Wix, Webflow, WordPress, or client-side JavaScript, use a Restricted Domain Key. Unlike Standard Keys, it is specifically designed for code that is publicly accessible.
No restricted public keys configured.
All current system workloads are processing via your server-side configurations.
Using Wix, Webflow, WordPress, or a drag-and-drop builder? You don't need backend code. Simply copy your key above and follow our HTML drop-in guide to add OTP verification to your forms in minutes.
Tip: You can also find all guides via the "Integrations" dropdown in the main site header.
Building a custom stack with Node.js, Next.js, Python, or Go? Inject your Secret Key securely into your server's .env file. Do not expose this key to the frontend client.