Developer API Documentation
Integrate LeadVerifier directly into your CRM, Zapier, Make, forms, or custom backend to verify, enrich, and score B2B leads in real-time.
1. Authentication
All REST API requests require a valid API key passed via the standard HTTP Authorization header or the X-API-Key header.
Authorization: Bearer lv_live_your_api_key_here # or X-API-Key: lv_live_your_api_key_here
You can generate and revoke API keys from your Developer Settings dashboard.
2. Single Lead Verification
POST /api/v1/verify/singlePerforms real-time 10-point analysis (website health, DNS records, email deliverability, business presence, technology stack detection, industry classification, sales opportunities, and quality scoring).
Request Example
curl -X POST https://leadensity.com/api/v1/verify/single \
-H "Authorization: Bearer lv_live_..." \
-H "Content-Type: application/json" \
-d '{
"company": "Apex Cloud Solutions",
"website": "https://github.com",
"email": "contact@apexcloud.io",
"phone": "+1 (415) 555-0192"
}'
Response Example (200 OK)
{
"success": true,
"data": {
"website_status": "online",
"http_status_code": 200,
"has_https": 1,
"email_valid_format": 1,
"email_domain_exists": 1,
"email_mx_exists": 1,
"email_provider_type": "business",
"detected_industry": "Software & SaaS",
"score": 92,
"quality": "excellent",
"technologies": ["React", "Google Analytics", "Cloudflare"],
"opportunities": [
{
"name": "Missing Schema.org Structured Data",
"service": "Technical SEO & Schema Optimization",
"priority": 5
}
]
}
}
3. Batch Lead Verification
POST /api/v1/verify/batchVerifies up to 25 leads synchronously in a single request. Deducts the corresponding lead count from your monthly subscription quota.
Request Example
curl -X POST https://leadensity.com/api/v1/verify/batch \
-H "Authorization: Bearer lv_live_..." \
-H "Content-Type: application/json" \
-d '{
"leads": [
{"company": "First Co", "website": "https://first.com", "email": "info@first.com"},
{"company": "Second Co", "website": "https://second.org", "email": "team@second.org"}
]
}'
4. Projects API
GET /api/v1/projectsFetch all verification projects or query specific leads within a project.
# List projects curl -H "Authorization: Bearer lv_live_..." https://leadensity.com/api/v1/projects # Get project details & paginated leads curl -H "Authorization: Bearer lv_live_..." https://leadensity.com/api/v1/projects/123?page=1&per_page=50
5. Quota & Usage API
GET /api/v1/usageCheck current period consumption, remaining credits, and active plan limits.
{
"success": true,
"plan": {
"name": "Pro",
"lead_limit": 5000,
"ai_limit": 500,
"project_limit": 50
},
"usage": {
"leads_processed": 1420,
"ai_generations": 110,
"exports": 18,
"period_start": "2026-08-01",
"period_end": "2026-08-31"
}
}
6. Verifying Webhook Signatures
LeadVerifier sends automated HTTP POST requests with a signature header X-LeadVerifier-Signature calculated via HMAC-SHA256 of the raw payload using your webhook signing secret.
PHP Verification Snippet
$payload = file_get_contents('php://input');
$sigHeader = $_SERVER['HTTP_X_LEADVERIFIER_SIGNATURE'] ?? '';
$secret = 'whsec_your_signing_secret';
$expectedSig = hash_hmac('sha256', $payload, $secret);
if (!hash_equals($expectedSig, $sigHeader)) {
http_response_code(401);
die('Invalid webhook signature');
}
$event = json_decode($payload, true);
// Process event: $event['event']
7. HTTP Error Statuses
| Code | Meaning | Description |
|---|---|---|
| 200 | OK | The request succeeded. |
| 400 | Bad Request | Missing required parameters or malformed JSON. |
| 401 | Unauthorized | Missing or invalid API Key. |
| 403 | Quota Exceeded | Monthly lead verification limits reached. Upgrade required. |
| 404 | Not Found | The requested project or resource does not exist. |
| 429 | Rate Limited | Too many requests sent in a short interval. |