> For the complete documentation index, see [llms.txt](https://docs.dataimpulse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataimpulse.com/proxies/parameters/session-id.md).

# Session Id

Learn how to use the session-id parameter with DataImpulse proxies to maintain sticky sessions and keep the same IP across multiple consecutive requests.

`sessid` - Connect to a specific IP address for 30 minutes. The value for `sessid`can be any string or number.

It's not a replacement for Sticky proxies, but rather an alternative when you want to connect to a specific IP address for an average of 30 minutes.

{% hint style="info" %}
Real people provide residential IPs, and if the IP provider you are using goes offline, your IP will be automatically replaced with another available one.
{% endhint %}

**Example:**

```
curl -x "http://login__cr.au;sessid.123:password@gw.dataimpulse.com:823" https://api.ipify.org/
```

Using `__cr.au;sessid.123` signifies that the client wants to connect to an IP address labeled as 123 in Australia (e.g., IP 154.6.151.212).

```
curl -x "http://login__cr.au;sessid.45:password@gw.dataimpulse.com:823" https://api.ipify.org/
```

Similarly, `cr.au;sessid.45` indicates the client's request for an IP address labeled as 45 in Australia (e.g., IP 38.55.106.76).

When you connect to the proxy via `__cr.au;sessid.123` you will consistently be assigned the IP address 154.6.151.212 for the entire 30-minute duration.  Likewise, connecting with `__cr.au;sessid.45` will result in the IP address 38.55.106.76 being assigned.

{% hint style="info" %}
Ensure that the port is specified in the settings as 824 for Socks5 or 823 for HTTPS.
{% endhint %}

<br>


---

# 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://docs.dataimpulse.com/proxies/parameters/session-id.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.
