> For the complete documentation index, see [llms.txt](https://ontime.gitbook.io/ontime-v1-old/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/ontime-v1-old/features/url-aliases.md).

# URL Aliases

{% 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](/ontime-v1-old/main-concepts/blocks/settings/url-aliases-settings.md)
{% endhint %}

URL Aliases is a feature with two main targets in mind

### Unnatended screens

We try to allow a worlkflow for integrating unnatended screens into the app network. Using a signage browser renderer or the screen integrated browser we can render any of the ontime pages. However this process is usually slow.

With URL Aliases you can define dynamic URLs that are changed from the app side:

We could for example setup the screen browsers to use an URL related to its 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`, as necessary

### Simplifying long URLs

Specifically in the case of lower thirds, ontime offers the possibility to modify the appearence of the views through parameters passed in the URL. However this can be slow and difficult to enter in the browser rendered (OBS, vMIX, d3 and so on). You might also want to quickly change this centrally to match styling for a specific event

In this case you could use an alias to shorten an url to something generic:

The custom url `lower?bg=ff2&text=f00&size=0.6&transition=5` could be simply called `mylower` or `shelleventlower` for quickly recalling


---

# 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/ontime-v1-old/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.