# Proxy List Parameters #### Proxy List Protocol Datacenter and Static Residential Proxies can be accessed via two distinct protocols, either: HTTP or SOCKS5. Each protocol may have its own unique port to connect to and therefore, when generating a proxy list, the protocol should be specified to recieve the correct port to connect to from the proxy object. #### Proxy List Version Datacenter and Static Residential Proxies can be either IPv4 or IPv6, though currently, only IPv4 is sold on the website. Some proxies may also be dual-stack, meaning they are made from an IPv4 and IPv6 address attached on the same server. To receive the correct IP address to connect to, please specify the correct version. At the time of writing (05/01/2024), ipv4 should be chosen in almost all cases. #### Proxy List Format Proxies can be displayed in various different formats as shown below: ``` socks5://user:password@192.168.1.3:8080 user:password@192.168.1.3:8080 192.168.1.1:8080:user:pass ``` These different formats are used by different softwares and systems to ingest proxies. You can set the requested format for the list to be in by using the list\_format parameter. #### Proxy List Authorization As mentioned, there are two types of ProxyUser authentication, those being username/password or IP Authorization. The proxy list will include different information depending on which is chosen and you should use the correct type in the Proxy List By Search API Route call. #### Proxy User ID As mentioned, multiple different proxy\_users can be given access to various different services on a single customer account. The Proxy List By Search API Route needs to know which proxy user to use in the list so that it can generate the list with the correct username and password. It therefore requires you to specify the intended proxy\_user\_id otherwise the default ProxyUser will be used. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://internal.developer.documentation.private.user.pingproxies.com/proxy-exporting/proxy-list-parameters.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.