Service
Email verification API
Connect a signup form, SaaS product, or CRM. REST API with Bearer key and OpenAPI documentation.
- OpenAPI
- API keys in dashboard
- Bulk and single endpoints
curl -X POST https://propercheck.pl/api/v1/verify \
-H "Authorization: Bearer ev_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"email":"user@company.com"}'Key management
Create multiple API tokens, rotate them, and disable individual keys without affecting the rest of your integration. Each key can serve a different environment: production, staging, bulk cron.
API error codes
401 — missing or invalid token. 402 — no credits. 422 — invalid email in payload. 429 — rate limit. Full specification in the OpenAPI documentation.
- 401 Unauthorized — check Authorization: Bearer header
- 402 Payment Required — top up credits in the dashboard
- 422 Unprocessable — fix email format in JSON
-
Create a token
Dashboard → API → generate a Bearer key.
-
Call verify
POST with JSON {"email":"user@company.com"}.
-
Handle the result
Valid → save the lead. Invalid → show an error in the form.
“We cleaned 40k leads before a cold email push. Bounce dropped from 9% to under 1% — domain reputation recovered.”
“We upload a CSV from CRM every week. Export with statuses saves hours of manual checking.”
“Trial credits were enough to judge quality. Then we bought a pack for our B2B newsletter.”
Related
Frequently asked questions
What is the API latency?
Typically seconds. It depends on the recipient mail server and current load.
What happens when credits run out?
The API returns a 402 error. Top up credits in the dashboard.
Can I test the API for free?
After signup you get free test credits. Use them on staging before production.