An IP enrichment API adds context to an address. The important question is which context: a company association, network operator, approximate location and website visitor identity are different outputs.
At Leadpipe, the IP to Company API answers a specific question: what stored company information is available for this IPv4 or IPv6 address? It is a useful building block for company research and qualification. It does not return a person, session history or every category of IP intelligence.
Match the API to the job
| Your goal | Output to look for | Mistake to avoid |
|---|---|---|
| Research a company associated with an address | Company name, website and available firmographics | Assuming the company legally owns the address |
| Understand network infrastructure | Network operator and documented network fields | Treating an ISP as the end user’s employer |
| Adapt a regional experience | Appropriate location fields with documented meaning | Treating a network location as a person’s precise address |
| Identify eligible website visitors | Visitor records and activity from an identification product | Expecting an IP company response to name the visitor |
| Find domains hosted on an IP | A reverse-IP hosting lookup | Treating hosted websites as visiting companies |
Before integrating, write down the entity your downstream system expects. A CRM account, a person and a network record should not share an ambiguous “identity” field.
What an IP-to-company response can contain
Providers expose different schemas. Snitcher offers an IP-to-company API, while ipapi.is describes an IP-to-company database. Review each product’s actual response, access terms and usage model rather than assuming the category name implies equivalent coverage.
Leadpipe’s current schema includes company name, website, business category, industry, employee count and location fields. It also includes fields that may be empty or null. Read the firmographic data guide for deciding which attributes matter to your account workflow.
The mapping is stored and provider-reported. It may be stale. A successful lookup does not establish that someone from that company visited your site unless you also have appropriate activity evidence. It does not establish which employee acted.
A Leadpipe lookup, from input to decision
1. Prepare one address
The endpoint accepts one IPv4 or IPv6 address without a URL, port, CIDR suffix or IPv6 zone identifier. It normalizes IPv6 spelling and treats IPv4-mapped IPv6 as the equivalent IPv4 address.
Use addresses your application is authorized to process. If a proxy supplies the address, establish the trusted network boundary before relying on forwarded metadata. Do not treat an arbitrary client-supplied header as verified origin evidence.
2. Send the request from your backend
The documented operation is GET /v1/data/company, authenticated with the organization’s X-API-Key. Keep the API key in your backend or secret manager. Use the official quickstart for the current request example and host.
An active key and eligible organization are required. The company API is separate from the browser pixel and visitor-retrieval endpoints. Installing a pixel does not replace API authentication.
3. Branch on company versus null
| Response | What it means | Next action |
|---|---|---|
data is an object |
A stored company result is available | Review company association and required fields |
data is null |
No successful company identity is stored | Preserve the unknown result |
| HTTP error | The request or service could not complete normally | Handle the documented error category |
A null result starts no enrichment job. Repeated polling is not a way to wait for one. Avoid converting unknown into “consumer,” “not a business” or “bad lead.”
4. Read usage with the result
A company-returning request consumes one company-lookup unit, including repeated requests for the same address. A null result consumes zero. meta supplies the consumed amount and the period’s limit, used and remaining allowance.
The allowance is organization-wide, shared across API keys and equal to the effective identification-plan limit for eligible organizations. Other products do not consume it. This is a separate allowance, not a claim that all API operations have the same billing rules.
5. Respect storage and retry behavior
The endpoint returns Cache-Control: no-store. Do not cache or prefetch responses. Do not import generic enrichment advice that recommends storing every response for reuse into this integration.
After an uncertain response, an automatic retry may consume another unit if it returns a company. Make that possibility visible in your recovery policy. Record operational status and allowance changes without unnecessarily retaining response data or credentials.
Rate limits are not the same as exhausted allowance
Leadpipe documents 60 requests per minute per client IP. Rate-limit headers describe request pacing, while successful-response meta describes company allowance.
For a pacing limit, respect the documented Retry-After value. For exhausted company allowance, stop until the billing allowance resets or is increased. A short sleep does not solve allowance exhaustion.
Invalid input, authentication, access and service failures also have different remedies. Use the endpoint reference instead of treating every non-200 response as “no company.”
Evaluate useful output, not just filled fields
For a permitted test sample, define which company fields you require and how you can independently check them. Keep disputed company associations separate from missing employee counts. Do not call a record accurate merely because its website resolves.
Shared networks, VPNs and hosting infrastructure are useful review categories. They can make the relationship between an address and a business uncertain. No provider should receive credit for a guessed association simply because your application requires a nonempty company field.
Use the record-review worksheet to track accepted, rejected and unresolved results. Calculate operational usefulness for your own application; this guide does not publish an unmeasured vendor accuracy ranking.
FAQ
Is IP enrichment the same as reverse DNS?
No. Reverse DNS retrieves a hostname associated with an address. IP enrichment may add company or other context from a provider’s data. A hostname is not a verified employer or person.
Can IP enrichment identify a visitor’s email?
Do not assume it can. Leadpipe’s company endpoint returns no people or visit data. Evaluate visitor identification separately if that is the output you need.
Does Leadpipe run fresh enrichment for each address?
No. The documented company endpoint retrieves stored company information. A null result does not queue new enrichment.
Build the right company workflow
Review the IP to Company product page and current API documentation, then confirm account eligibility and plan allowances. If you need the broader website-identification workflow, start with Leadpipe: 7 days or 500 profiles, whichever comes first, no card.
Sources and review basis
Published by Leadpipe. Vendor references support product descriptions; recommendations reflect our assessment of fit. Confirm current plan and contract terms before buying.
