--- title: Adding HTTP Targets slug: zen-master/adding-http-targets docTags: createdAt: 2024-12-27T19:19:17.125Z --- ZEN Master supports six types of HTTP Targets: - **HTTP** – the Channel is pushed to any HTTP server via HTTP PUT methods. This option also includes the ability to use secure HTTPS protocol. - **YouTube** - the channel is pushed to YouTube - **S3 Bucket** – the Channel is pushed to an AWS S3 storage service. - **MediaStore** - the Channel is pushed to an AWS Elemental MediaStore storage service. - **GCP Storage **– the Channel is pushed to a Google GCP storage service. - **Azure** – the Channel is pushed to Azure Blob storage. As part of the Target configuration, you will assign the Target to an existing Channel, as the Target will only become functional once a Channel is attached to it. However, it is possible to add a Channel to a Target after the initial configuration. The selected Channel has been configured to provision the Egress Cluster (Processing Cluster setting) and the specific Broadcaster/s within this cluster (Target Broadcaster/s setting). The following procedure describes how to add an HTTP Target in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. **To add a new HTTP Target:** :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Targets**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Target** window is displayed. ::Image[]{src="https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/zvFxXsgvX6d6ikzJ2Qcmd_image.png" size="80" width="730" height="1406" position="center" alt="Create New Target window" darkWidth="730" darkHeight="1406" showCaption="false"} ::: :::WorkflowBlockItem Click on **HTTP**. The **Create New HTTP Target** window is displayed. ::Image[]{src="https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/AMf12C8qoXwQxlr7vuqeZ-20260209-202047.png" size="70" width="1330" height="3030" position="center" alt="Create New HTTP Target" darkWidth="1330" darkHeight="3030" showCaption="false"} ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a logical name for the HTTP target. ::: :::WorkflowBlockItem In the **Tags** field, select one or more of the predefined Tags from the drop-down list. Tags are used for access control. By selecting a Tag you are relating this target to that Tag. Tags are associated with certain roles (through the Users & Roles screen), and roles, in turn, are associated with users and user groups. If you would like to create a new Tag, see [Creating a Tag](docId\:YpM9tw81ap6nq8sTKv4Rd) . ::: ::::WorkflowBlockItem In the **Events Configuration Profile** field, select from the dropdown list the profile that you would like to apply to this Target. By default, the Default profile is applied. :::hint{type="info"} *Events Profiles *consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. ::: :::: :::WorkflowBlockItem The Target's location is used to represent it in the proper position in the Map display (see [Maps](docId\:sFZM6JvoRvuigo7X0dNUE)). By default, the location is determined automatically based on the Target's IP. If you would like to manually set the location of the Target (Optional), use the following procedure: 1. Click on the **Edit** icon next to the **Location **field. A search box is shown below the **Location** field. 2. Enter identifying info for the location (e.g. street address, zip code, coordinates). Search results are displayed below the search box as you type. 3. Click on the desired location. The selected location populates the **Location** field. ::: ::::WorkflowBlockItem In the **Configuration** section, in the **Channel** field, select from the drop-down list the channel that will be sent to the target. (Optional field) :::hint{type="info"} The target will only become functional once a channel has been assigned to it. However, you can configure the target settings and then add a channel to the target after the initial configuration. ::: :::: :::WorkflowBlockItem In the **Type** field, select one of the following options: - Azure – the channel is pushed to Azure Blob storage. - GCP Storage - the channel is sent to a GCP storage service. - HTTP – the channel is sent to an HTTP server. - MediaStore – the channel is pushed to an AWS Elemental MediaStore storage service. - S3 Bucket – the channel is sent to an AWS S3 bucket storage service. - TAMS - the channel is sent to a [TAMS](docId\:Xb6n9zuNCcGOdDaBrvsba) repository. - YouTube – the Channel is sent to YouTube. ::: :::WorkflowBlockItem Enter the required information for the selected Target type as follows: - For Target type *HTTP *– 1. In the **Encapsulation** section, select the type of encapsulation used, options are *HLS *or *CMAF* (*DASH + fMP4 HLS)*. 2. In the **Ingest URL** field, enter the Ingest URL of the HTTP server to which the Channel will be pushed. - For Target type *TAMS* - - In the **TAMS API URL** field, enter the URL for API access to your TAMS instance. - Check **Ignore Certificate** if you don't want sending streams because a certificate is faulty or not detected. - Enter the OAuth **Client ID** that is used to authenticate API requests to TAMS. - Enter the OAuth **Secret Key** that is used to authenticate API requests to TAMS. - Enter the **Authorization Token URL** used to retrieve authorization tokens. - For Target type YouTube – - In the **Encapsulation** section, select HLS. - In the **Ingest URL** field, enter the Ingest URL provided by YouTube to which the Channel will be pushed. - In the **YouTube Stream Key** field, enter the stream key that is provided by YouTube. - For Target type *S3 Storage*– 1. In the **Encapsulation** section, select the type of encapsulation used, options are *HLS *or *CMAF (DASH + fMP4 HLS)*. 2. In the **S3 URI **field, enter the URI of the S3 bucket. 3. In the **Region** field, select from the drop-down list the AWS Region of the S3 bucket. 4. In the **Access Key ID** field, enter the Access Key ID used to access your AWS account. 5. In the **Secret Access Key** field, enter the secret Access Key used to access your AWS account. - For Target type *MediaStore* – 1. In the **Encapsulation** section, select the type of encapsulation used, options are *HLS *or *CMAF (DASH + fMP4 HLS)*. 2. In the **MediaStore URI** field, enter the URI of your MediaStore storage service. 3. In the **Region** field, select from the drop-down list the AWS region of your storage service. 4. In the **Access Key ID** field, enter the access key ID for your MediaStore account. 5. In the **Secret Access Key** field, enter the Secret access key ID for your MediaStore account. - For Target type *GCP *– 1. In the **Encapsulation** section, select the type of encapsulation used, options are *HLS *or *CMAF (DASH + fMP4 HLS)*. 2. In the **GCP Account **field, select an account from the drop-down list. 3. In the **Ingest URL** field, enter the Ingest URL of the GCP storage service to which the channel will be pushed. - For target type *Azure* – 1. In the **Encapsulation** section, select the type of encapsulation used, options are *HLS* or *CMAF (DASH + fMP4 HLS)*. 2. In the **Azure Account** field, select a linked account from the drop-down list. 3. In the **Ingest URL** field, enter the Ingest URL of the Azure storage service to which the channel will be pushed. ::: ::::WorkflowBlockItem In the **Playback URL** field, enter an alternative URL for playback and HLS validation. :::hint{type="info"} For an S3 bucket target this field is optional, if no URL is entered then ZEN Master will use the URL of the S3 bucket for playback and validation. For an HTTP server target ZEN Master will not validate the stream or enable playback unless a URL is entered in this field. ::: :::: :::WorkflowBlockItem Select the **Upload DVR playlist** checkbox if you are streaming a recorded/VOD stream and you want to upload a DVR playlist in addition to the live playlist. ::: :::WorkflowBlockItem Select the **Delete Outdated** checkbox if you would like ZEN Master to delete any outdated fragments from the server. (Default: selected) ::: :::WorkflowBlockItem In the **Propagate Tags to S3/MediaStore objects**, select this checkbox if you want ZEN Master to create AWS backend tags for the Tags, which were assigned to this HLS target, and propagate them to S3 and/or MediaStore objects. These tags will be applied to the manifest, the chunks, and folders. ::: :::WorkflowBlockItem Select the **Ignore Certificate** checkbox if you are sending the stream to a trusted server which does not have a valid certificate. When this option is selected, the Zixi Broadcaster will ignore TLS certificate errors and send the stream to its destination. ::: :::WorkflowBlockItem If you would like to receive alerts for subtitles missing from the stream, select the **Alert on missing WebVTT captions** checkbox and then in the Search Window field, enter the number of seconds of missing subtitles to generate the alert. (Default: 30 seconds) ::: :::WorkflowBlockItem In the **Initial State** section, select the **Disabled** checkbox if you would like to disable this Target upon initial configuration. ::: ::::WorkflowBlockItem Select the **Muted** checkbox if you would like to disable error/recovery notifications for this Target upon initial configuration. :::hint{type="info"} You canIn the Protections field, Enable/Unmute the Target at any time. ::: :::: :::WorkflowBlockItem Under **Protections**, select the **Channel reassignment protection** chekbox if you want to prevent the reasssignment of this Target to another Channel. This is helpful in cases where you are switching the channel on multiple targets at once and can accidetaly select a Target that should not have been switched to the new Channel. ::: :::WorkflowBlockItem If you would like to configure advanced settings, click on **Advanced **and enter values for the desired fields - see the **Paramaters Table **below for explanations of the fields. ![](https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/KZGQYLddm2vpVnpeFff4L_http-target-advanced.png) ::: :::WorkflowBlockItem Click **Save**. ::: ::::: **HTTP Target Configuration Parameters Table** | **Parameter** | **Description** | | --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the HTTP Target in ZEN Master. | | Tags | Select one or more of the predefined Tags from the drop-down list.
Tags are used for access control. By selecting a Tag, you are relating this Target to that Tag. Tags are associated with certain roles (through the Users & Roles screen), and roles, in turn, are associated with users and user groups. If you would like to create a new Tag, see [Creating a Tag](docId\:YpM9tw81ap6nq8sTKv4Rd). | | Events Configuration Profile | Select from the dropdown list the profile that you would like to apply to this Target. By default, the *Default* profile is applied.
Note: *Events Profiles* consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Location (Optional) | The Target's location is used to represent it in the proper position in the Map display (see ). By default, the location is determined automatically based on the Target's IP. Enter identifying info for the location (e.g. street address, zip code, coordinates) and select the desired location from the suggestions that are shown. | | ***Configuration*** | | | Channel
(Optional) | Select from the drop-down list the Channel that will be sent to the Target. | | Type | Select one of the following options:
* Azure – the Channel is pushed to Azure Blob storage. * GCP - the Channel is sent to a GCP storage service. * HTTP – the Channel is sent to an HTTP server. * MediaStore – the Channel is pushed to an AWS Elemental MediaStore storage service. * S3 Bucket – the Channel is sent to an AWS S3 bucket storage service. * YouTube - the Channel is sent to YouTube. | | ***For HTTP Type*** | | | Encapsulation | Select the type of encapsulation used. Options are: *HLS* or *CMAF (DASH + fMP4 HLS)*. | | Ingest URL | Enter the Ingest URL of the HTTP server to which the channel will be pushed. | | ***For the TAMS Type*** | | | TAMS API URL | The URL for API access to your TAMS instance. | | Ignore Certificate | Check the box if you don't want sending streams because a certificate is faulty or not detected. | | Client ID | Client ID use to authenticate API requests to your TAMS instance. | | Secret Key | Secret Key use to authenticate API requests to your TAMS instance. | | Authorization Token URL | URL used to retrieve authorization tokens for your TAMS instance. | | ***For YouTube Type*** |
| | Encapsulation | Select the type of encapsulation used. Options are *HLS only*. | | Ingest URL | Enter the Ingest URL provided by YouTube to which the Channel will be pushed. | | YouTube Stream Key | Enter the stream key that is provided by YouTube. | | ***For S3 Storage Type*** | | | Encapsulation | Select the type of encapsulation used. Options are: *HLS* or *CMAF (DASH + fMP4 HLS)*. | | S3 URI | Enter the URI of the S3 bucket. | | Region | Select from the drop-down list the AWS Region of the S3 bucket. | | Access Key ID | Enter the Access Key ID used to access your AWS account. | | Secret access Key | Enter the secret Access Key used to access your AWS account. | | Propagate Tags to S3/MediaStore objects | Select this checkbox if you want ZEN Master to create AWS backend tags for the Tags, which were assigned to this HLS target, and propagate them to S3 and/or MediaStore objects. These tags will be applied to the manifest, the chunks, and folders. | | ***For MediaStore Type*** | | | Encapsulation | Select the type of encapsulation used. Options are: *HLS* or *CMAF (DASH + fMP4 HLS)*. | | MediaStore URI | Enter the URI of your MediaStore storage service. | | Region | Select from the drop-down list the AWS region of your storage service. | | Access Key ID | Enter the Access Key ID for your MediaStore account. | | Secret Access Key | Enter the Secret Access Key ID for your MediaStore account. | | Propagate Tags to S3/MediaStore objects | Select this checkbox if you want ZEN Master to create AWS backend tags for the Tags, which were assigned to this HLS target, and propagate them to S3 and/or MediaStore objects. These tags will be applied to the manifest, the chunks, and folders. | | ***For GCP Type*** | | | Encapsulation | Select the type of encapsulation used. Options are: *HLS* or *CMAF (DASH + fMP4 HLS)*. | | GCP Account | Select an account from the drop-down list.
Note: To connect a GCP Account to ZEN Master, see [Linking a Google GCP Account](docId\:JBuzi2tJvSpS3o_VzVXxH). | | Ingest URL | Enter the Ingest URL of the GCP storage service to which the Channel will be pushed. | | ***For Azure Type*** | | | Encapsulation | Select the type of encapsulation used. Options are: *HLS* or *CMAF (DASH + fMP4 HLS)*. | | Azure Account | Select a linked account from the drop-down list.
Note: To connect an Azure account to ZEN Master, see [Linking an Azure Account](docId\:jSST1KXHRRRFCdyc1lENl) . | | Ingest URL | Enter the Ingest URL of the Azure storage service to which the Channel will be pushed. | | ***For All Types*** | | | Playback URL | Enter an alternative URL for playback and HLS validation.
Note: For an S3 bucket Target this field is optional, if no URL is entered then ZEN Master will use the URL of the S3 bucket for playback and validation. For an HTTP server Target ZEN Master will not validate the stream or enable playback unless a URL is entered in this field. | | Upload DVR playlist | Select this checkbox if you are streaming a recorded/VOD stream and you want to upload a DVR playlist in addition to the live playlist. | | Delete Outdated | Select this checkbox if you would like ZEN Master to delete any outdated fragments from the server. (Default: selected) | | Ignore Certificate | Select this checkbox if you are sending the stream to a trusted server which does not have a valid certificate. When this option is selected, the Zixi Broadcaster will ignore TLS certificate errors and send the stream to its destination. | | Alert on missing WebVTT captions | If you would like to receive alerts for subtitles missing from the stream, select this checkbox. Note: Even if this checkbox is not selected, ZEN Master will monitor the subtitles and validate them with the stream, but you will not receive notifications for missing subtitles. | | ***Initial State*** | | | Disabled | Select this checkbox if you would like to disable this Target upon initial configuration. | | Muted | Select this checkbox if you would like to disable error/recovery notifications for this Target upon initial configuration. | | ***Protections*** | | | Channel reassignment protection | Select this option if you want to prevent the reasssignment of this Target to another Channel. This is helpful in cases where you are switching the channel on multiple targets at once and can accidetaly select a Target that should not have been switched to the new Channel. | | ***Advanced*** | | | Billing Code | If you would like to track usage for this Target, enter your **Billing Code** details, see . (Supported for Broadcasters v14.8+) | | Billing Password | Enter the password that corresponds to this billing code. | | Billing Channel ID | An optional arbitrary string - you can enter anything you want to for your record-keeping. This is **not** related to ZEN Master Channels. | | Segment Path | Select one of the following path segmentation types:
**Full path** – in this option the path would be constructed as follows: \/\/\?\
**Path in parameters** - in this option the path would be constructed as follows: \?\
**Flat path** - in this option the path would be constructed as follows: \/\\_\?\. Any "/" in path should be replaced with "\_" | | Upload Type (for CMAF encapsulation) | Select the specific type:
* DASH * DASH & fMP4 HLS * fMP4 HLS |