# URL Parameters

If your application needs a client-side integration to pass parameters or any other information to communicate with your application, you can pass dynamic launch flags for each session.

For example, in order to add `-token MY_TOKEN` flag to your application launch flags for a specific `Stream Session`, you should only add `?launchFlags=-token%20MY_TOKEN` at the end of the Stream URL with the parameter, you would like to send. Please note that the launch flags should be URL safe.

```
https://app.vagon.io/stream/_STREAM_ID_?launchFlags=-token%20MY_TOKEN
```

{% hint style="warning" %}
URL Parameters are applied for each Stream Session individually while the Stream Session is starting up. It won't affect any other `Stream Session`.
{% endhint %}

## Launch Parameter Reset - Start New Session with Different Launch Parameters

Launch parameters are set for each user session separately and stored in local storage to apply the same launch arguments if any connection or initialization issue during the connection phase.

If your use case requires sending different launch arguments to the same Stream session, you have to add a `newSession=true` parameter at the end of your Stream URL to reset previous launch arguments.

If you are using `launchFlags` with your Stream URL, you can use both of them by adding & between them.

```
https://app.vagon.io/stream/_STREAM_ID_?launchFlags=-token%20MY_TOKEN&newSession=true
```

{% hint style="info" %}
URL parameters are only supported for the Streams using [Vagon Application Streaming](/streams/vagon-application-streaming.md). URL Parameter support will be added for Pixel Streaming and Render Streaming projects in the future.
{% 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://docs.vagon.io/streams/integrations/url-parameters.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.