> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.quortex.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# What is the structure of a Quortex Play publishing point?

Let's see how publishing points can help you customize endpoint URLs used by players!

# General structure

A **publishing point** on Quortex Play is the HTTPS endpoint a player will use to access a stream.

New publishing points are automatically added when you add inputs, processing configurations, or targets to a pool.

The general structure of a publishing point is as follows:

> https :// ${color}[#4a5568](<pool_id>) .live.quortex.io / ${color}[#f05e88](<input>) / ${color}[#8161ff](<processing>) / ${color}[#0fc2ba](<target>) / ${color}[#4a5568](index.<extension>)

Let's break it down:

* ${color}[#4a5568](<pool_id>) is an unique identifier for your pool, it cannot be changed.
* ${color}[#f05e88](<input>) is the identifier of your choice for each input. Its default value is generated using the input name.
* ${color}[#8161ff](<processing>) is the identifier of your choice for each processing configuration. Its default value is generated using the processing configuration name.
* ${color}[#0fc2ba](<target>) is the identifier of your choice for each target. Its default value is generated using the target name.
* ${color}[#4a5568](<extension>) depends on the target type, it cannot be changed.

Example publishing point URLs:

https :// ${color}[#4a5568](j6r3vxpj) .live.quortex.io / ${color}[#f05e88](wildlife_channel) / ${color}[#8161ff](hd) / ${color}[#0fc2ba](dash) / ${color}[#4a5568](index.mpd)
https :// ${color}[#4a5568](j6r3vxpj) .live.quortex.io / ${color}[#f05e88](wildlife_channel) / ${color}[#8161ff](hd) / ${color}[#0fc2ba](hls) / ${color}[#4a5568](index.m3u8)

# Going further

The neat thing about publishing points is that you can customize them the way you want, without changing the names of components themselves. Think of this as "public identifiers vs internal names"!

## Customizing identifiers

You can change the **hd** identifier of the "HD" processing configuration to **premium**:


![](https://storage.crisp.chat/users/helpdesk/website/9845223dbfb4e800/changingidentifier_14kpzdo.jpg)
![](https://storage.crisp.chat/users/helpdesk/website/9845223dbfb4e800/changeidentifier_6v6h5.gif)

The identifier will change in the two publishing points simultaneously.

## Disabling a publishing point

You can also disable a specific combination of input, processing and target:

![](https://storage.crisp.chat/users/helpdesk/website/9845223dbfb4e800/disablepublishingpoint_1ba71t0.gif)

That endpoint will be unavailable for players.

## Disable a whole component

You can also disable a whole component:


![](https://storage.crisp.chat/users/helpdesk/website/9845223dbfb4e800/disablecomponent_1h6bjal.gif)

If you do that, be sure to create a rule that will select the appropriate component, because we won't find it in the URL anymore!
For example, you could create an **Always** rule selecting the "HD" processing configuration:

![](https://storage.crisp.chat/users/helpdesk/website/9845223dbfb4e800/processingrule_1n520im.png)

As a result, the following endpoints will use the "HD" processing configuration, even if it's not in the URL:

https :// ${color}[#4a5568](j6r3vxpj) .live.quortex.io / ${color}[#f05e88](wildlife_channel) / ${color}[#0fc2ba](dash) / ${color}[#4a5568](index.mpd)
https :// ${color}[#4a5568](j6r3vxpj) .live.quortex.io / ${color}[#f05e88](wildlife_channel) / ${color}[#0fc2ba](hls) / ${color}[#4a5568](index.m3u8)

That's it, have fun with publishing points!