Making Requests
This guide covers how to make requests through the Ping Residential Proxy Gateway, including parameter configuration and code examples.
Basic Request Structure
All requests follow standard HTTP/HTTPS proxy protocols. You’ll need to:
- Specify the proxy endpoint
- Provide authentication credentials
- Make your request to the target URL
Authentication
Authentication is handled through proxy user credentials in the format:
To obtain credentials, please contact our support team.
Request Parameters
You can customize your proxy requests by adding parameters to the username string. Parameters are separated by hyphens (-
).
Username Format
Available Parameters
Country Code (cc
)
Status: ✅ Available
Select a specific country for your proxy request.
- Parameter:
cc
- Format: ISO Alpha-2 country code (case-insensitive)
- Example:
cc-US
for United States,cc-GB
for United Kingdom
Example username with country selection:
City (city
)
Status: 🚧 Coming Soon
Target a specific city within a country.
- Parameter:
city
- Format: City name in English (case-insensitive)
- Example:
city-London
,city-NewYork
Session ID (sessid
)
Status: 🚧 Coming Soon
Maintain the same IP address across multiple requests.
- Parameter:
sessid
- Format: Alphanumeric string (0-9, A-Z)
- Session Duration: up to 10 minutes
- Example:
sessid-abcde12345
Complete Parameter Example
Once all parameters are available, you’ll be able to combine them:
Code Examples
Random Proxy (Default)
Make a request through a random residential proxy:
cURL
Python (requests)
Node.js (axios)
Country-Specific Proxy
Route your request through a specific country:
cURL
Python (requests)
Node.js (axios)
Response Handling
The proxy gateway returns the response from your target URL unchanged. Handle responses according to your target API’s documentation.
Error Codes
Common proxy-related errors:
- 407 Proxy Authentication Required - Invalid credentials
- 429 Too Many Requests - Rate limit exceeded
- 503 Service Unavailable - No proxies available for the specified parameters
Best Practices
- Use HTTPS endpoint when possible for better security
- Handle errors gracefully - Implement retry logic for temporary failures
- Respect rate limits - Avoid overwhelming the proxy service
- Keep credentials secure - Never commit credentials to version control
Need Help?
Contact our support team for:
- Credential requests
- Technical assistance
- Feature requests