How does IPRout handle IPv4?
Pass a dotted-decimal address such as 8.8.8.8 to GET /ip/{ip}. IPRout validates the address, resolves its geographic and Autonomous System context, and returns the standard JSON response. The same authentication, error handling, quota accounting, and usage monitoring used for caller lookup apply to explicit IPv4 lookup, so applications can share one client implementation across both modes.
Which IPv4 data is available?
A successful response can include continent, country, region, city, timezone, UTC offset, approximate coordinates, ASN, network organization, currency, and calling code. Country and network-level attributes are generally more suitable for product decisions than city or coordinates. Clients should support null optional fields and ignore unfamiliar additive fields so response evolution does not break an otherwise valid integration.
What can applications build with IPv4 context?
Useful patterns include selecting regional content, preselecting country and timezone values, enriching analytics events, grouping traffic by ASN, and giving support or operations teams better request context. Security teams can combine network data with existing risk signals. IP location should not become the only control for account access, payment approval, legal eligibility, or any decision requiring exact physical location.
What IPv4 limitations matter?
Many users share a public IPv4 address through home routers, carrier-grade NAT, company gateways, or public Wi-Fi. Hosting and VPN addresses may represent a data center rather than the end user. Address ownership and routing also change over time. These realities mean the response is network intelligence, not a personal identity record, and retention should follow the minimum needs of the application.
How do I make an IPv4 request?
Authenticate over HTTPS and put the validated address in the path. The example below uses the public resolver address documented throughout IPRout. Check for HTTP 422 before decoding a success model, stop on HTTP 401, and inspect usage after HTTP 429. A ten-second timeout is a conservative starting point that applications can tune from observed behavior.
curl --fail-with-body --max-time 10 \
-H "Authorization: Bearer $IPROUT_API_KEY" \
https://api.iprout.com/ip/8.8.8.8How should IPv4 lookup scale?
Use a named key per service where plan capacity permits so consumption and revocation remain isolated. Watch total and per-key usage through /usage, keep concurrency bounded, and avoid immediate repeated retries. Pro customers can create a key with a workload-specific cap from 100 to 1,000,000 requests; that cap contains the key but does not add to the shared monthly account allowance.
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.
- Standard dotted-decimal input
- Consistent JSON response
- Country through network-owner context
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.