Extract emails, phone numbers, and places from any webpage.
Contact Extractor scrapes public email addresses, phone numbers, and physical addresses from any web page URL. It tallies the findings and returns unique records found on the page.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
"url": "https://en.wikipedia.org/wiki/Email_address",
"emails": [
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]"
],
"phones": [],
"places": [
"China",
"Japan",
"Russia",
"Rajasthan",
"India"
],
"emailCount": 27,
"phoneCount": 0,
"placeCount": 5,
"uniqueDomains": [
"example.com",
"example.org",
"s.example",
"EasierReading.org",
"pobox.com"
]
}
}
About the Contact Extractor API
Contact Extractor works by extracting contact data from a website URL using web scraping techniques. It returns the contact emails, phone numbers, and places found on the website.
What people use it for
- Sales Prospecting Enrichment
- Sales reps scan company contact pages to extract direct support emails and phone numbers before launching targeted outbound calling campaigns.
- Local Directory Aggregation
- When curating regional merchant directories, indexing bots scrape storefront websites to verify physical street addresses and telephone lines.
- Vendor Onboarding Verification
- Before approving newly registered suppliers, procurement portals check listed corporate websites to confirm published business locations and operational telephone numbers.
- Talent Sourcing Workflows
- To build candidate pipelines, recruiting platforms scrape agency team pages to discover public email addresses for key department heads.
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Contact Extractor
Same data, same APIVerve account, same credit balance — one key works on all of them.
What types of contact details does it extract from a page?
Does it crawl entire websites or only the specified URL?
Are unique email domains included on the Free plan?
Can I remove the cap on how many contacts are returned?
What would 5,000 page extractions a month cost me?
Can I store the extracted contact data in my own CRM or lead list?
Request parameters — POST /v1/contactextractor
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
urlRequired | string | https://en.wikipedia.org/wiki/Email_address | The URL of the web page to extract contact data from url |
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
limitOptionalPremium | number | 5 | Limits the number of found contact details found on the page. Set -1 for unlimited default 5 |
curl -X POST "https://api.apiverve.com/v1/contactextractor" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://en.wikipedia.org/wiki/Email_address","limit":-1}'Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
content-typeRequired | POST body | application/json |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — POST /v1/contactextractor
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"url": "https://en.wikipedia.org/wiki/Email_address",
"emails": [
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]"
],
"phones": [],
"places": [
"China",
"Japan",
"Russia",
"Rajasthan",
"India"
],
"emailCount": 27,
"phoneCount": 0,
"placeCount": 5,
"uniqueDomains": [
"example.com",
"example.org",
"s.example",
"EasierReading.org",
"pobox.com"
]
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
url | string | "https://en.wikipedia.org/wiki/Email_address" | The web page URL that was scraped, echoed back from the request |
emails | array | [[email protected], ...] | Unique email addresses found on the page, in order of appearance and capped at `limit` |
phones | array | [] | Unique phone numbers found on the page, in order of appearance and capped at `limit` |
places | array | [China, ...] | Unique places or street addresses found on the page, in order of discovery and capped at `limit` |
emailCount | number | 27 | Number of email addresses included in the `emails` array |
phoneCount | number | 0 | Number of phone numbers included in the `phones` array |
placeCount | number | 5 | Number of places included in the `places` array |
uniqueDomainsPremium | array | [example.com, ...] | Unique domains extracted from the returned `emails` (e.g., example.com, company.org) |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 10 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Contact Extractor calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 20 | Free |
| Starter | $29.99 | 200,000 | 20,000 | $1.50 |
| Pro | $99.99 | 1,000,000 | 100,000 | $1.00 |
| Mega | $299.99 | 4,000,000 | 400,000 | $0.75 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — POST /v1/contactextractor
No SDK to install — this is a plain HTTPS call to /v1/contactextractor with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/contactextractor" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — POST /v1/contactextractor
Install the Node.js SDK, then call the Contact Extractor API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/contactextractorconst res = await fetch("https://api.apiverve.com/v1/contactextractor", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — POST /v1/contactextractor
Install the Python SDK, then call the Contact Extractor API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-contactextractorimport requests
res = requests.get(
"https://api.apiverve.com/v1/contactextractor",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — POST /v1/contactextractor
Install the C# / .NET SDK, then call the Contact Extractor API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.ContactExtractorusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/contactextractor");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — POST /v1/contactextractor
No SDK to install — this is a plain HTTPS call to /v1/contactextractor with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/contactextractor", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — POST /v1/contactextractor
No SDK to install — this is a plain HTTPS call to /v1/contactextractor with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/contactextractor");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — POST /v1/contactextractor
No SDK to install — this is a plain HTTPS call to /v1/contactextractor with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/contactextractor")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Contact Extractor form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Contact Extractor API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Contact Extractor API.
Data Scraping
- Contact Extractor
- Link Scraper
- SEO Data Scraper
- Website Images Scraper
- Website Screenshot
Related articles
All articles →
Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read 
Automating Visual Testing With ScreenshotsCatch visual bugs before users do. Here's how to add screenshot-based testing to your workflow.Read 
Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read