> For the complete documentation index, see [llms.txt](https://docs.vdo.ninja/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vdo.ninja/advanced-settings/setup-parameters/push.md).

# \&push

The stream ID that you are publishing with will be the defined value

Sender-Side Option! ([`&room`](/advanced-settings/setup-parameters/room.md))

## Aliases

* `&id`

## Options

Example: `&push=StreamID`

<table><thead><tr><th width="186">Value</th><th>Description</th></tr></thead><tbody><tr><td>(no value given)</td><td>creates a randomly generated stream ID</td></tr><tr><td>(string)</td><td>1 to 64-characters long. Non-alphanumeric characters are sanitized to <code>_</code>; case sensitive.</td></tr></tbody></table>

## Details

`&push` is the parameter that tells VDO.Ninja to be a publisher.

<https://vdo.ninja/?push=streamid>\
<https://vdo.ninja/?view=streamid>

If the parameter is not provided, a randomly generated stream ID will be used instead.\
<https://vdo.ninja/?push>

This is a useful parameter if you wish to reuse an invite link or if you refresh the page often.\
The value can be up to 64-characters long and is case sensitive.\
If left empty, the stream ID will default to a random one.

For a persistent OBS/browser-source setup, give the guest a planned `&push=STREAMID` and use the matching `&view=STREAMID` link in OBS. See [Permanent links, reusable invites, and stream IDs](/guides/how-to-get-permanent-links.md) for examples and alternatives such as `&permaid`, scenes, and slots.

{% hint style="info" %}
If the stream ID is already in active use, an error will be shown and the stream will not publish.
{% endhint %}

If using a [`&room`](/advanced-settings/setup-parameters/room.md) URL and not using [`&scene`](/advanced-settings/mixer-scene-parameters/scene.md) or [`&solo`](/advanced-settings/mixer-scene-parameters/and-solo.md), VDO.Ninja will automatically generate a `&push` ID.

## Related

{% content-ref url="/pages/nflQf8jCCEjl8n8TWEcm" %}
[\&permaid](/advanced-settings/setup-parameters/and-permaid.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MZdw7J4MWj\_hoTqT9Kh" %}
[\&view](/advanced-settings/mixer-scene-parameters/view.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MZfzezMF7\_FyjAq8Dze" %}
[How to get permanent links](/guides/how-to-get-permanent-links.md)
{% endcontent-ref %}


---

# 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.vdo.ninja/advanced-settings/setup-parameters/push.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.