How is a specific address looked up?
Append the address to the /ip route and authenticate the GET request. IPRout resolves the supplied value, not the network address of the caller. GET /ip/8.8.8.8 is therefore deterministic with respect to the requested address even when it is called from another country or behind a proxy. IPv4 and IPv6 use the same endpoint and return the same field model.
Which workflows need explicit lookup?
Explicit lookup is appropriate when an address already exists in an event or record. An operations tool can enrich login events, an analytics worker can add country and ASN fields, and a support dashboard can show broad network context for a customer-reported connection. Server-side batch or queue workers can use the same endpoint, provided they remain within the account allowance and avoid uncontrolled retry loops.
How should IP input be validated?
Reject empty or obviously malformed values before making a request, but let the API provide the authoritative HTTP result for supported address input. An invalid explicit address returns HTTP 422 and should not be retried until the value changes. Encode path values correctly, particularly IPv6 notation, and never concatenate untrusted input into shell commands or logs. Keep the original event separate from the enrichment result.
What does the response prove?
The response describes the best available location and network assignment for the requested address. It does not prove that a specific person controlled the address, that the device was at the returned coordinates, or that the network organization is the end user's employer. NAT, shared gateways, VPNs, hosting providers, and address reassignment all limit that interpretation. Use it as contextual evidence with appropriate uncertainty.
How do I test an explicit lookup?
Use 8.8.8.8 while building because the documentation provides its complete example response. Store IPROUT_API_KEY outside source code, use HTTPS, set a finite timeout, and inspect the status before parsing JSON. After the integration works, replace only the final path value with an address from your validated server-side workflow.
curl --fail-with-body --max-time 10 \
-H "Authorization: Bearer $IPROUT_API_KEY" \
https://api.iprout.com/ip/8.8.8.8How should repeated lookups be managed?
Monitor the volume attributable to the service's named key and compare it with the shared account allowance through GET /usage. Cache results only when suitable for your product and retention policy, since network assignments can change. Bound concurrency for background jobs, stop retrying permanent 401 or 422 failures, and use delayed, limited retries for transient network or server failures.
Which IPRout plan fits this workload?
Use the 7-Day Developer Key for a short evaluation with 1,000 requests. Free supports ongoing low-volume use with 10,000 monthly requests and 1 active key. Starter adds 100,000 requests, 2 active keys, and up to 5 exact CORS origins per key. Pro provides 1,000,000 requests, 5 active keys, up to 10 origins per key, and a configurable 100 to 1,000,000 request cap when each key is created. All active account keys consume one shared monthly allowance.
| Plan | Monthly requests | Active keys |
|---|---|---|
| Free | 10,000 | 1 |
| Starter | 100,000 | 2 |
| Pro | 1,000,000 | 5 |
What are the key benefits?
This feature uses the same authenticated HTTPS interface and predictable JSON conventions as the rest of IPRout. That keeps the integration small while letting teams separate product logic from the details of IP intelligence and API key controls.
- Enrich stored IP events
- Investigate network context
- Process addresses in server-side workflows
How do I get started?
Generate a 7-Day Developer Key for evaluation or create an account key for an ongoing integration. Begin with the documented request, add status-aware error handling and a finite timeout, then connect only the response fields your product needs. Review usage before launch, keep the secret in trusted infrastructure, and follow the linked documentation for feature-specific configuration.