Skip to content
Tomba home
Start free

// web scraping

SocksNode

Residential, mobile and datacenter proxies for the page-fetching step of your lead-generation workflows, with country, city and ISP targeting set in the proxy username.

View IntegrationSetup Guide
  1. 01
    SocksNode proxies for web scrapingIn SocksNodeWeb Scraping
  2. via api key
  3. 02

    Tomba API

    GET/email-finder1 search credit
  4. 03

    Result

    richard@piedpiper.comvalid

// 01 · overview

Tomba in SocksNode

Proxies for the Page-Fetching Step with SocksNode

SocksNode provides residential, mobile and datacenter proxies for scrapers, scripts and workflow tools. Use them in the step that fetches company or directory pages, then pass the company domains to Tomba to find and verify the contacts.

SocksNode Products Available

  • Rotating residential proxies: real home IPs, paid per GB, a new IP per request or a sticky session
  • Rotating mobile proxies: 4G/5G carrier IPs, paid per GB
  • Rotating datacenter proxies: fast datacenter IPs, paid per GB
  • 24-hour residential IPs: one chosen home IP for 24 hours
  • Static ISP and datacenter IPs: one address rented for a period

Benefits of SocksNode

  • Pay per GB: bandwidth you buy does not expire, no subscription
  • HTTP, HTTPS and SOCKS5: works in any scraper, script or workflow node
  • Targeting in the username: country, city and ISP are set by adding a part to the proxy username
  • Sticky sessions: hold one IP for a session of up to 24 hours
  • API: create and manage proxies programmatically

Common Workflows

  1. Automated Lead Generation: Fetch public company pages through SocksNode → Collect the company domains → Find emails with Tomba → Verify → Save to database
  2. Directory Collection: Fetch listing pages from a given country → Extract companies → Enrich with Tomba
  3. Local Market Research: Load pages as a visitor in another country sees them → Collect companies and domains → Find decision-maker emails
  4. Outreach Automation: Collect domains → Find emails → Verify → Personalize message → Send via email tool

Getting Started

  1. Create a SocksNode account and add bandwidth
  2. Create proxy credentials in the SocksNode dashboard
  3. Open the proxy settings of your scraper, script or workflow node
  4. Enter host global.socksnode.com, port 9000 (HTTP) or 11000 (SOCKS5), your username and password
  5. Add the country to the username, for example USERNAME-country-de
  6. Fetch a page, then pass the company domains to Tomba

Visit our documentation and the Tomba setup guide for step-by-step instructions.

// 02 · endpoints

The API behind Tomba for SocksNode

Integrations call the same Tomba endpoints as your code, with your account's credits. Each call costs what its endpoint costs.

01GET/domain-search1 per 10 search credits02GET/author-finder1 search credit03GET/email-verifier1 verification credit04GET/technologyFree

// customers

What teams say about Tomba

  • I like that it allows me to find my leads by simply using a domain name or the name of a person from a specific domain. I also like that it allows me to export my prospects to my CRM. It helps save me a lot of time on my sales process.
    Hugo H.CMOvia G2
  • Tomba.io is very fast and has lots of features to help anyone prospect and find exactly who you need to find. I use my zoom.info and Apollo to find companies for lead gen and then run those leads into tomba to grab me prospect info in record time.
    Julian M.Account Executive, Insightvia G2

// quick start

Make your first call in a minute

Free account, real API key, the same endpoints Enterprise customers use.

  1. 1Create a free account25 searches a month. No card.
  2. 2Copy your key and secretFrom API keys in the dashboard.
  3. 3Call the APIPaste the request; the answer is JSON.
Get free API keyRead the docs
curl "https://api.tomba.io/v1/email-finder?domain=piedpiper.com&first_name=Richard&last_name=Hendricks" \
  -H "X-Tomba-Key: $TOMBA_API_KEY" \
  -H "X-Tomba-Secret: $TOMBA_SECRET_KEY"
Response
200 OK· 1 search credit
{
  "data": {
    "email": "richard@piedpiper.com",
    "first_name": "Richard",
    "last_name": "Hendricks",
    "full_name": "Richard Hendricks",
    "website_url": "piedpiper.com",
    "company": "Pied Piper",
    "pattern": "{first}",
    "department": "executive",
    "type": "personal",
    "position": "CEO",
    "country": "US",
    "gender": "male",
    "twitter": null,
    "linkedin": "https://www.linkedin.com/in/richard-hendricks",
    "score": 100,
    "accept_all": false,
    "phone_number": true,
    "verification": {
      "date": "2025-01-15T10:32:00+01:00",
      "status": "valid"
    },
    "sources": [
      {
        "uri": "https://piedpiper.com/blog/engineering",
        "website_url": "piedpiper.com",
        "extracted_on": "2024-06-01T09:14:07+01:00",
        "last_seen_on": "2025-01-10T17:02:44+01:00",
        "still_on_page": true
      }
    ],
    "phone_data": []
  }
}