GET /v1/data/company is the legacy stored lookup. For enrichment, free ISP results, and dedicated credits, use the current IP2Company API.
The legacy endpoint retains its existing response and billing rules. Moving an integration requires using the current endpoint and enabling IP2Company access; an existing key or legacy company allowance alone does not grant that access.
Read a stored legacy result
Use an active organization API key with company-lookup access. Replace the illustrative address with your IP:data with classification, accessType, isInternetProvider, and available company fields. Missing or unsuccessful saved results return data: null. Neither a stored association nor a missing result proves IP ownership or visitor employment.
The legacy payload has data and meta; it does not expose the current product’s top-level status, stale, refreshStatus, or polling guidance.
Legacy credits and limits
A non-null
data object is not enough to infer a charge. Inspect meta.credits_consumed. Repeated organization-returning lookups consume another unit.
The allowance is shared organization-wide Company Credits, configured by a plan or active override. Company Visitors admissions also use it. Legacy plans can retain their effective identification-plan limit as the default company allowance. It is separate from current IP2Company credits.
Legacy responses expose meta.limit, meta.used, and meta.remaining. Once the allowance is exhausted, all lookups are refused before source access, even requests that might otherwise be free.
Requests are limited to 60 per minute per client IP. Rate-limit headers describe pacing; meta describes the billing allowance. Honor Retry-After for temporary limits. Exhausted billing allowance requires a reset or increase.
Do not cache, prefetch, or blindly retry an uncertain response: another successful organization-returning request consumes another unit. These legacy rules do not apply to current IP2Company usage.
See the legacy endpoint reference for the generated schema and errors.