# \&autowhep

[WHIP Option](/steves-helper-apps/whip-and-whep-tooling.md) / Sender-Side Option! ([`&push`](/advanced-settings/setup-parameters/push.md))

## Options

Example:

`&whipout=https%3A%2F%2Fexample.com%2Fstream%2Fwhip&autowhep`

| Value            | Description                                     |
| ---------------- | ----------------------------------------------- |
| (no value given) | Attempts to infer and advertise a WHEP play URL |

## Details

`&autowhep` is an opt-in helper for WHIP publishing links. If a WHIP output URL is configured with [`&whipout`](/advanced-settings/whip-parameters/and-whipout.md), [`&whippush`](/advanced-settings/whip-parameters/and-whipout.md), or [`&pushwhip`](/advanced-settings/whip-parameters/and-whipout.md), and no explicit [`&whepshare`](/advanced-settings/whip-parameters/and-whepshare.md) value is already set, VDO.Ninja will try to derive the matching WHEP playback URL and share it with room peers.

This is useful when each guest has a known WHIP publishing endpoint and you want the other guests/viewers to pull that guest via WHEP instead of direct peer-to-peer media.

Known URL patterns include:

| WHIP pattern                                           | WHEP pattern                    |
| ------------------------------------------------------ | ------------------------------- |
| Cloudflare Stream `.../{publish-token}/webRTC/publish` | `.../{playback-id}/webRTC/play` |
| `.../whip`                                             | `.../whep`                      |
| `.../webRTC/publish`                                   | `.../webRTC/play`               |
| `.../publish`                                          | `.../play`                      |

Explicit [`&whepshare`](/advanced-settings/whip-parameters/and-whepshare.md) values take priority. If you use [`&whepsharetoken`](/advanced-settings/whip-parameters/and-whepsharetoken.md), it will still be attached after the WHEP URL is auto-derived.

`&autowhep` does not change the default WHIP behavior; it only runs when added to the sender URL.

## Related

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

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

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


---

# 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.vdo.ninja/advanced-settings/whip-parameters/and-autowhep.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.