# Residential Proxy List

As Residential Proxy services are not sold per IP address, the List Route is slightly different to the Proxy List By Search or Proxy List by ID routes previously discussed, though some list parameters are shared.

{% content-ref url="/pages/MnUTW2ibou6sM644TRRn" %}
[Proxy List Parameters](/proxy-exporting/proxy-list-parameters.md)
{% endcontent-ref %}

#### Sticky Vs Rotating

One additional parameter in the Residential Proxy List API Route is list\_session\_type. This parameter is used to instruct the function on whether to return a list of proxies which rotate on every single request or are sticky (try to stay static for as long as possible).

More information about different session types is attached:

{% content-ref url="/pages/ACMdWdNxY6loK8wMO0VO" %}
[Sticky Vs Rotating (Vs Static)](/residential-package-management/sticky-vs-rotating-vs-static.md)
{% endcontent-ref %}

**Geographical Location**

Residential Proxy Services are not region specific and they are able to access the Residential Proxy Network which spans over 190 countries and thousands of different cities.

To ensure they are accessing proxies from the correct location in the network, the user can specify a country\_id or city\_id / city\_alias and the list that is returned will represent proxies from those locations if the values are valid. If no geographical parameters are entered then the network randomly assigns proxies to requests.

The API has several routes to inform on available country\_id and city\_id options, they are:

```
/private/user/country/search
/private/user/city/search
```

There are thousands of cities in the database so the usual user flow would be to allow a customer to select a country and then presenting them with a list city returned from the City Search API Route while specifying the country\_id in the search call.

{% hint style="info" %}
It is usually recommended that customers create proxies at a country-level rather than a city level so there is enough peers in the network in that region to allow for good performance.
{% endhint %}


---

# 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/residential-package-management/residential-proxy-list.md?ask=<question>
```

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.