> For the complete documentation index, see [llms.txt](https://ontime.gitbook.io/v2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ontime.gitbook.io/v2/features/url-aliases.md).

# URL Aliases

Custom aliases allow providing a short name for any ontime URL.

It serves two primary purposes:

* [Providing dynamic URLs for automation or unattended screens](#url-automation)
* [Simplifying complex URLs](#simplifying-complex-or-lengthy-urls)

{% hint style="info" %}
The URL Aliases feature means to provide aliases to the parameters section of the url, ie: the bit after ontime's port.\
192.168.10.1:4001/**`THIS-HERE`**

See more in the [URL Aliases Settings](broken://pages/an1KYgAHNKguUERdNx5R)
{% endhint %}

### URL Automation

URL Automation is meant for cases in which we would like to change the URL from Ontime without the need for changes on the consumers of the views.

Consider the case of unattended screens or hardware integrations, where access to change the browser URL may be impractical

{% hint style="info" %}
Example

We could for create an alias for a specific screen that relates to its role, position or type\
eg: `192.168.10.10:4001/thirdfloor`

And in Ontime, configure `thirdfloor` to be an alias to any of the views such as `public` or `backstage`, eventually also changing this throughout the event without need for changes in the third floor viewer
{% endhint %}

### Simplifying complex or lengthy URLs

With the view customisations through URL parameters, the URL can become complex, making recreating and sharing difficult.

Leveraging URL Aliases, you can create a simple URL that can encode a view with given styles.

{% hint style="info" %}
Example

The custom url `lower?bg=ff2&text=f00&size=0.6&transition=5` could be simply called `mylower o`r `shell-event-lower` or quickly recalling
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ontime.gitbook.io/v2/features/url-aliases.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.