Understanding how proxy objects relate to geographic and network entities in the Ping Proxies API
The Ping Proxies API organizes resources in a hierarchical structure that mirrors the real-world relationships between network and geographic entities. Understanding these relationships is crucial for effectively managing and filtering proxies.
Residential Proxy Generation and Object Relationships
Residential proxies differ from datacenter and ISP proxies in that they’re generated on demand rather than being persistent objects. When generating residential proxies, you specify geographic and network attributes to target specific types of exit nodes.
If you’re conducting market research for a new retail location, you might want to check product availability and pricing from the perspective of consumers in specific cities:
To explore the available ASNs, countries, subdivisions, and cities, you can use the corresponding search endpoints:
Copy
# List all available ASNscurl --request GET \ --url 'https://api.pingproxies.com/1.0/public/user/asn/search' \ --header 'X-API-Public-Key: your_public_key' \ --header 'X-API-Private-Key: your_private_key'# List all cities in a specific countrycurl --request GET \ --url 'https://api.pingproxies.com/1.0/public/user/city/search?country_id=gb' \ --header 'X-API-Public-Key: your_public_key' \ --header 'X-API-Private-Key: your_private_key'
By understanding these object relationships, you can more effectively utilize the Ping Proxies API to precisely target and manage your proxy infrastructure according to your specific needs.