1. Standard Access Keys
Designed exclusively for private, secure server environments.
Private Backend Server Only
For security, old keys are hidden. Roll the key to generate a new one.
Security Credentials
Manage your environment keys. Choose the correct architectural pipeline for your deployment framework below.
Synchronizing with edge router...
OR
2. Restricted Domain Keys
Public SafeSite Builders & Frontend Developers: If you are integrating Authepy directly into a frontend environment like Wix, Webflow, WordPress, or standard client-side JS scripts where code is publicly viewable, do not use a Standard Key. Instead, provision a Restricted Domain Key.
🛡️ Core Edge Verification Protocol:
When this key layout is utilized, Authepy's global edge router enforces mandatory cryptographic origin validation. Any OTP requests originating from unlisted domains or external terminals are rejected instantly at the edge.
No restricted public keys configured.
All current system workloads are processing via your server-side configurations.
How to Integrate Authepy
No-Code & Site Builders
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.
Backend Developers
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.