Reverse IP Lookup
The company and contact details associated with a visitor's IP address.
curl -X POST https://api.1lookup.dev/v1/reverse-ip-lookup \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"ip":"203.0.113.42"}'{
"success": true,
"data": {
"ip": "203.0.113.42",
"matched": true,
"match_level": "contact",
"company": {
"name": "Northwind Logistics",
"domain": "northwind.example",
"industry": "Logistics and supply chain",
"employee_range": "201-500",
"location": {
"city": "Columbus",
"state": "OH",
"country": "US"
}
},
"contacts": [
{
"full_name": "Marcus Bell",
"job_title": "Director of Operations",
"email": "marcus.bell@example.com"
}
],
"network": {
"isp": "Example Business Fiber",
"connection_type": "business"
}
},
"meta": {
"credits_used": 10,
"credits_remaining": 999,
"cached": false,
"request_id": "req_8f3a2c1e9b7d"
}
}Authorization
Authorizationstring<bearer>requiredYour API key as a Bearer token. Live keys start with 1lk_live_. Test keys start with 1lk_test_ and return this endpoint's sample response without spending credits. See authentication.
Body
Send the fields as a JSON object with Content-Type: application/json.
ipstring<ip>requiredIP address. IPv4 or IPv6 Example: 203.0.113.42
freshbooleanSkip the 7-day cache and run a new lookup. Charged as a normal lookup.
referencestringYour own identifier, echoed back in meta and shown in lookup history.
Response
A 200 response carries the result in data and the cost of the call in meta. These are the fields most integrations read.
successbooleantrue when the lookup ran.
data.matchedbooleanTrue when the address resolves to a company. False results are not charged.
data.match_levelstringcompany when only the organization is known, contact when contact-level data came back as well.
data.company.namestringThe business the address was resolved to.
data.company.domainstringThe company's website domain, ready to pass to firmographic or contact lookups.
data.company.industrystringA plain-language industry label for segmenting and routing.
data.company.employee_rangestringHeadcount band, such as 51-200 or 201-500.
data.contactsarrayContact-level records tied to the address, where available. Often an empty list.
data.network.connection_typestringbusiness, residential, mobile or hosting. It explains why some addresses have no company behind them.
meta.credits_usednumberCredits charged for this call.
meta.credits_remainingnumberYour balance after the call.
meta.cachedbooleantrue when the result came from the 7-day cache.
meta.request_idstringQuote this when you contact support.
Errors
A failed request returns success: false with an error object, and is never charged. The full list is on the errors page.
| HTTP | Code | Meaning |
|---|---|---|
| 401 | unauthorized | The key is missing, malformed or revoked. |
| 402 | insufficient_credits | Your credits are used up and pay as you go is off or at its limit. |
| 422 | invalid_input | A field is missing or malformed. The field property names it. |
| 429 | rate_limited | Too many requests for this key. Wait for the Retry-After interval. |
| 500 | internal_error | Something failed on our side. Safe to retry. |
| 503 | source_unavailable | An upstream source did not answer in time. Safe to retry. |
Billing
10 credits / match. Charged only when a match is found. Errors are never charged, and repeating the same input within 7 days is served from cache at no charge.
Product overview and use cases