Implementation Guide
Integrate Pyzit across your entire stack. From instant frontend feedback to robust backend security.
Choose your strategy
Frontend
Improve UX by alerting users immediately as they type in your signup forms.
Backend
The source of truth. Block disposable emails at the database level during registration.
Scripts
Use our Bulk API to clean legacy databases and marketing lists at scale.
Backend Integration (Recommended)#
Always perform validation on your server. This prevents users from bypassing your security by disabling client-side scripts.
Standard Flow
Receive Request → Call Pyzit API → Allow/Deny Signup → Save to DB
Before you begin, ensure you have created an API token with the necessary scopes.
Frontend Integration#
Provide instant feedback to your users. We recommend calling your own backend which then proxies the request to Pyzit to keep your API token secure.
Security Warning: Never call the Pyzit API directly from the browser using your primary API token. It will be exposed to users.
Integration Best Practices
Fail-Safe Implementation
Always wrap your API calls in try/catch blocks. If the Pyzit API is unreachable or returns an error, your application should "fail open" and allow the user to register to avoid blocking legitimate signups.
Environment Secrets
Store your API tokens in environment variables (e.g., PYZIT_TOKEN). Never hardcode them in your source code or commit them to version control.