> For the complete documentation index, see [llms.txt](https://doc.sk5data.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.sk5data.com/dynamic-residential/session-types.md).

# Session Types

The session type determines how residential IP addresses are assigned to your requests. We offer two session modes: **Rotating Sessions** and **Sticky Sessions**, allowing you to choose how frequently your IP address changes based on your business needs.

### Rotating Sessions

A new residential IP address is automatically assigned for each request.

* **Key Advantage:** High anonymity, helping reduce the risk of rate limiting and IP blocking.
* **Use Cases:** Large-scale web scraping, search engine results collection, ad verification, and other concurrent tasks that do not require persistent sessions.

### Sticky Sessions

Multiple requests will continue to use the same residential IP address for a specified period.

* **Key Advantage:** Maintains session continuity, making it ideal for tasks involving logins, multi-step form submissions, or shopping cart processes.
* **Use Cases:** Social media account management, e-commerce price monitoring, and automated tasks that require persistent login sessions.

**Configuration Example:**

Add `-sid-{session_id}-ttl-{duration}` to your username to configure a sticky session. The duration is specified in minutes.

**Format:** `username-sid-{session_id}-ttl-{duration}`

**Example:** `GURXROr7-sid-Y-ttl-10` (keeps the same IP address for 10 minutes within the session).

**Examples:**

```
username-sid-Z-ttl-5:password
username-sid-5Is-ttl-60:password
username-sid-xpDfo9-ttl-120:password
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.sk5data.com/dynamic-residential/session-types.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.