Contact Extractor API

Overview

To use Contact Extractor, you need an API key. You can get one by creating a free account and visiting your dashboard.

POST Endpoint

https://api.apiverve.com/v1/contactextractor

Example

How to call the Contact Extractor API in different programming languages.

curl -X POST \
  "https://api.apiverve.com/v1/contactextractor" \
  -H "X-API-Key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
  "url": "https://en.wikipedia.org/wiki/Email_address",
  "limit": -1
}'

const response = await fetch('https://api.apiverve.com/v1/contactextractor', {
  method: 'POST',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    "url": "https://en.wikipedia.org/wiki/Email_address",
    "limit": -1
})
});

const data = await response.json();
console.log(data);

import requests

headers = {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
}

payload = {
    "url": "https://en.wikipedia.org/wiki/Email_address",
    "limit": -1
}

response = requests.post('https://api.apiverve.com/v1/contactextractor', headers=headers, json=payload)

data = response.json()
print(data)

package main

import (
    "fmt"
    "io"
    "net/http"
    "bytes"
    "encoding/json"
)

func main() {
    payload := map[string]interface{}{
        "url": "https://en.wikipedia.org/wiki/Email_address",
        "limit": "-1"
    }

    jsonPayload, _ := json.Marshal(payload)
    req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/contactextractor", bytes.NewBuffer(jsonPayload))

    req.Header.Set("X-API-Key", "your_api_key_here")
    req.Header.Set("Content-Type", "application/json")

    client := &http.Client{}
    resp, err := client.Do(req)
    if err != nil {
        panic(err)
    }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}

{
  "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"
    ]
  }
}

Authentication

The Contact Extractor API requires authentication via API key. Include your API key in the request header:

X-API-Key: your_api_key_here

Learn more about authentication →

Interactive API Playground

Test the Contact Extractor API directly in your browser with live requests and responses.

Parameters

The following parameters are available for the Contact Extractor API:

Response

The Contact Extractor API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.

Other Response Formats

<?xml version="1.0" encoding="UTF-8"?>
<response>
  <status>ok</status>
  <error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
  <data>
    <url>https://en.wikipedia.org/wiki/Email_address</url>
    <emails>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
      <email>[email protected]</email>
    </emails>
    <phones>
    </phones>
    <places>
      <place>China</place>
      <place>Japan</place>
      <place>Russia</place>
      <place>Rajasthan</place>
      <place>India</place>
    </places>
    <emailCount>27</emailCount>
    <phoneCount>0</phoneCount>
    <placeCount>5</placeCount>
    <uniqueDomains>
      <uniqueDomain>example.com</uniqueDomain>
      <uniqueDomain>example.org</uniqueDomain>
      <uniqueDomain>s.example</uniqueDomain>
      <uniqueDomain>EasierReading.org</uniqueDomain>
      <uniqueDomain>pobox.com</uniqueDomain>
    </uniqueDomains>
  </data>
</response>

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 Structure

All API responses follow a consistent structure with the following fields:

Learn more about response formats →

Response Data Fields

When the request is successful, the data object contains the following fields:

Headers

Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →

GraphQL AccessALPHA

Access Contact Extractor through GraphQL to combine it with other API calls in a single request. Query only the contact extractor data you need with precise field selection, and orchestrate complex data fetching workflows.

Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.

POST https://api.apiverve.com/v1/graphql

query {
  contactextractor(
    input: {
      url: "https://en.wikipedia.org/wiki/Email_address"
      limit: -1
    }
  ) {
    url
    emails
    phones
    places
    emailCount
    phoneCount
    placeCount
    uniqueDomains
  }
}

Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.

CORS Support

The Contact Extractor API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →

Rate Limiting

Contact Extractor requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →

Error Codes

The Contact Extractor API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →

SDKs for Contact Extractor

Official Contact Extractor packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →

JitPack

No-Code Integrations

Contact Extractor works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →

Zapier

Make

Pipedream

n8n

Power Automate

Frequently Asked Questions

People who used this also used...

Based on your interest in Contact Extractor, you might also like these APIs:

Website Screenshot

Web Screenshots is a simple tool for capturing screenshots of web pages. It returns an image screenshot of the web page provided.

20 credits per call

Website Images Scraper

Web Image Scraper is a simple tool for scraping images from a website. It returns the URLs of the images found on the website.

10 credits per call

SEO Data Scraper

SEO Scraper is a simple tool for scraping SEO data. It returns the meta title, meta description, and more.

5 credits per call