IP / Company Lookup

Enrichment Workflows (IP, Domain & Company Lookup Guide)

LeadBoxer’s Lookup APIs allow you to enrich your existing data with
firmographics, company intelligence, and person-level insights—without using the tracking pixel.

This guide explains how to use the Lookup APIs to:

  • enrich IP addresses
  • enrich companies/domains
  • turn a work email into a professional profile
  • build real-time or batch enrichment workflows
  • combine data with CRM, SaaS products or internal pipelines

1. When to Use Enrichment Workflows

Use Lookup APIs if you want to:

  • enrich CRM leads with company data
  • enrich inbound demo requests
  • enrich newsletter subscribers
  • reveal company behind an IP
  • run account identification in ABM workflows
  • augment your own SaaS platform with B2B intelligence
  • power dashboards, reports or onboarding flows
  • process batch data from warehouses or logs

Lookup APIs do not require the website pixel.
They can run fully independently in your backend.


2. Available Lookup Endpoints

LeadBoxer provides 3 enrichment types:

IP Lookup

Input: IP address
Output:

  • company domain
  • company name
  • industry
  • employee count
  • revenue range
  • location
  • ISP/type detection
  • confidence score

Use this when:

  • you track server logs
  • you want to identify companies accessing a product or API
  • you want ABM signals without browser tracking

Company/Domain Lookup

Input: domain (e.g., company.com)
Output:

  • company name
  • size (employees, revenue)
  • industry
  • technologies
  • location
  • many more fileds

Use this when:

  • enriching CRM accounts
  • scoring ICP fit
  • building account-based dashboards
  • running batch enrichment on pipeline data

Email Lookup

Input: work email address (name and company are optional hints)
Output:

  • full name and headline
  • LinkedIn profile URL
  • seniority and job function
  • location
  • languages
  • work experience (current and previous roles)

Available on every plan. Credits are only used when a profile is found. Use POST /v1/email-lookup (a GET form exists, but keeps the email in URLs and logs). See Email Lookup.

Use this when:

  • enriching form fills and sign-ups with the person behind the email
  • routing leads by role or seniority
  • replacing a person-enrichment API such as Clearbit Person

3. Making a Lookup Request

For full technical details see the API reference


4. Building Real-Time Enrichment Workflows

Use cases:

A. CRM Enrichment (HubSpot, Pipedrive, Salesforce)

When a new contact is created:

  1. Trigger webhook or automation
  2. Call the Lookup API
  3. Write firmographic/persona fields back into CRM
  4. Update lead score or pipeline stage

B. SaaS Product Sign-Up

When a user signs up in your product:

  1. Capture email and IP
  2. Call Lookup API for both
  3. Store enriched attributes in your user table
  4. Use enriched data to route onboarding or sales follow-up

C. Scoring Pipelines

Combine behavioural + profile data:

  • ICP score
  • Company size score
  • Persona match score

Use this to determine:

  • sales priority
  • onboarding path
  • ideal customer fit

Did this page help you?