Thunderbit Open API home page
SupportAPI Console
Recipes

Lead Enrichment

Enrich CRM leads from company websites with structured extraction

Given a list of company URLs (from your CRM, signup form, or manual upload), pull structured firmographic data — industry, employee count, tech stack, contact channels — and write it back to the lead record.

Schema

{
  "type": "object",
  "properties": {
    "companyName":   { "type": "string" },
    "industry":      { "type": "string", "description": "Primary industry from the homepage / about page" },
    "employeeCount": { "type": "string", "description": "Headcount band, e.g. '11-50'" },
    "headquarters":  { "type": "string", "description": "City, country" },
    "contactEmail":  { "type": "string" },
    "linkedinUrl":   { "type": "string" }
  },
  "required": ["companyName"]
}

Implementation

import httpx

API = "https://openapi.thunderbit.com/openapi/v1"
H = {"Authorization": "Bearer YOUR_API_KEY"}

leads = [
    {"id": "lead_1", "url": "https://acme.com"},
    {"id": "lead_2", "url": "https://stripe.com"},
]

job = httpx.post(f"{API}/batch/extract",
                 headers=H,
                 json={"urls": [l["url"] for l in leads],
                       "schema": SCHEMA,
                       "webhook": {"url": "https://your-server.com/webhook/leads",
                                   "secret": "whsec_..."}}).json()

When the webhook fires, join results[].url back to your lead IDs and write the structured fields to your CRM.

Tips

  • Keep required minimal — many small-company sites won't have every field
  • Add a "best-effort" pass: if contactEmail is missing, also distill the /contact page
  • Cache by domain — re-enriching the same domain monthly is usually enough

This recipe is being expanded with CRM integration patterns (HubSpot / Salesforce) — check back soon.

On this page

SchemaImplementationTipsRelated