Business data & lead enrichment
Public business pages.
Structured company records.
Collect company names, websites, categories and locations from pages you choose. Give your enrichment pipeline consistent fields instead of unstructured HTML.
data.extract{
"company": "Northstar Studio",
"website": "https://northstar.example",
"category": "Design services",
"city": "Berlin"
}Fictional company and illustrative extracted data.
Ask for company-level fields
POST this JSON body to /api/v1/scrape with your x-api-key header. Replace the illustrative URL with a company or directory page you are permitted to collect.
Start without extra rendering flags. If the details load through JavaScript, add use_js_render and wait for the relevant element. A default fetch with AI extraction is 8 tokens before other features or retries.
Check the API HTTP status and success, then read data.extract. Validate the fields and keep unavailable information empty. The extractor is not a contact verification service.
{
"url": "https://directory.example.com/company/northstar",
"extract_schema": {
"type": "object",
"properties": {
"company": {
"type": "string"
},
"website": {
"type": "string"
},
"category": {
"type": "string"
},
"city": {
"type": "string"
}
}
}
}From source pages to your CRM
01 · Define the source and purpose
Choose permitted directories or company pages. Record why you need each field; avoid collecting personal details simply because they are visible.
02 · Extract and validate
Store source URLs and collection times. Normalize domains, check company names and deduplicate records before enrichment.
03 · Import through your integration
Map the JSON to your CRM fields. Your application handles scoring, record updates, retention and any permitted outreach.
For multiple source URLs, use async batches. An MCP agent can use the same extraction options for research.
Collection is only one part of enrichment
Does public business data mean I can use it for outreach?
Not automatically. Check the source terms and your lawful basis for collection and use. Personal contact details can be regulated even when publicly visible. Respect applicable privacy, marketing and deletion requirements; this guide is not legal advice.
Does FineData find or verify email addresses?
This workflow extracts information visible on the pages you supply. It does not include email discovery, contact verification, lead scoring or outreach. Keep missing fields empty rather than inventing contact details.
Can I send results to my existing CRM?
Yes, through your own integration. Extract company-level fields as JSON, validate and deduplicate them, then map the data to your CRM import or API. FineData does not automatically sync or update CRM records.
How do I collect multiple directory pages?
Supply the individual page URLs through async batches, or use browser actions for a page that requires interaction. Pagination and deduplication remain part of your workflow. A single URL request does not automatically crawl the whole directory.
Public visibility does not remove privacy obligations or grant permission for marketing. Respect source terms and the Acceptable Use Policy. No rendering mode guarantees access to every directory.
Validate one record before collecting thousands
Check the source, output and actual tokens used. Failed scrapes are not billed.