Start using ISP Proxies

1

Set up a proxy user

To begin using Self-Service ISP Proxies, you'll need to set up a proxy user. Enter your chosen username and password, then click on Create proxy user. Be sure to save these credentials for future access. Proxy user credentials are your access to the IPs.

2

Run a request

Once setup is complete, you can now create and execute your first cURL request in a terminal or any other environment to test the ISP Proxies. ​ Send a query to https://ip.oxylabs.io/location using the command below, specifying port 8001 and your proxy credentials:

curl -x isp.oxylabs.io:8001 -U "user-USERNAME:PASSWORD" https://ip.oxylabs.io/location

3

Get a response

Upon executing this command, the output will display the IP address with your request. When connecting through port 8001, the same IP address assigned to this port will always be used. To switch to another IP, change the port to 8002, 8003, and so forth.

Get your proxy list

Access your proxy list in the dashboard by navigating to the My Products section, clicking on ISP Proxies, and selecting Proxy List.

What's included in a proxy list?

Entry point	A gateway for connecting to your proxies
Port	A designated port to access a specific proxy from your list
Country	The geographic location of your proxies
Assigned IP	A specific proxy IP assigned to the chosen port

Location settings

ISP proxy network offers country targeting. Simply send a request to the port associated with the desired location's assigned IP: ​

curl -x isp.oxylabs.io:8000 -U 'user-USERNAME:PASSWORD' https://ip.oxylabs.io/location

Protocols

Self-Service ISP Proxies support HTTP, HTTPS, and SOCKS5 protocols. For instance, to connect through an HTTPS protocol, you must specify this in your request by adding https:// to your entry point: ​

curl -x https://isp.oxylabs.io:8000 -U user-USERNAME:PASSWORD https://ip.oxylabs.io/location

Make sure that the libraries or third-party tools you intend to use are compatible with HTTPS and SOCKS5 protocols. ​

Here’s a code example with the SOCKS5 protocol: ​

curl -x socks5h://user-USERNAME:[e-mail]:8000 https://ip.oxylabs.io/location

Response codes

When using ISP Proxies, you may receive response codes that indicate specific reasons for success or failure. Here are the most common ones:

Response code	Error message	Description
400	Bad Request	This error code can be returned by a proxy server if the request did not specify a host to connect to or if there was a general error in parsing the HTTP request. Ensure that the request is correctly formed, including the URL, and try again.
407	Proxy Authentication Required	This response indicates that the request lacks proxy authentication information or the username or password is invalid. Include the Proxy-Authorization header in your request, verify that your username and password are correct, and then try again.
500	Internal Server Error	The proxy server has encountered an internal error. Retry the request at a later time. ​
502	Bad Gateway	This response signifies that the IP assigned to your session ID is no longer available or there are no exit nodes meeting your specified parameters (e.g., city, ASN) at the given time. To resolve this issue, you can wait for one minute for the system to assign a new IP address to your session ID or switch to a new session ID (i.e., change the sessid parameter) to receive a new IP address.
522	Timeout	The proxy server did not get a response from the upstream server in time. Retry the request.
525	No Exit Found	This custom HTTP status code means that the proxy could not find an exit node that satisfies the request. Adjust the request filter parameters or try again later.

🎯 Important: Find more information with codes samples in our documentation.

---

Head back to the dashboard