> For the complete documentation index, see [llms.txt](https://audalaxy.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://audalaxy.gitbook.io/docs/metaspreader-configuration-settings/metaspreader-configuration-settings.md).

# MetaSpreader configuration settings

MetaSpreader supports configuring your metadata receivers as JSON in the Console.

<mark style="background-color:blue;">Your Console</mark> > <mark style="background-color:blue;">Edit Channel</mark> > <mark style="background-color:blue;">Metaflow</mark> > <mark style="background-color:blue;">MetaSpreader</mark>

## Console

```json
{
    "radioplayer": {
        "stationid": "--old Station ID",
        "email": "-- email of account (required)",
        "apikey": "-- apikey (required)",
        "typ": "radioplayercloud"
    },
    "radio.de": {
        "broadcast": "",
        "apikey": "",
        "typ": "radio.de"
    },
    "jsonpush_1": {
      "channelname": "my audiostream name 1",
      "url": "https://playerwebsite1/metadata-input",
      "typ": "jsonpush"
    },
    "jsonpush_2": {
      "channelname": "my audiostream name 2",
      "url": "https://playerwebsite2/metadata-input",
      "typ": "jsonpush"
    },

}
```

## POST request with JSON payload

```json
{
    "jsonpush_1": {
        "channelname": "my audiostream name 1",
        "url": "https://playerwebsite1/metadata-input",
        "typ": "jsonpush"
    },
    "jsonpush_2": {
        "channelname": "my audiostream name 2",
        "url": "https://playerwebsite2/metadata-input",
        "typ": "jsonpush"
    },

}
```

{% hint style="info" %}
The content of POST is like [Metadata data-set reference](/docs/metadata-data-set-reference/metadata-data-set-reference.md)
{% endhint %}

## Radioplayer

```json
{
    "radioplayer": {
        "stationid": "--old Station ID",
        "email": "-- email of account (required)",
        "apikey": "-- apikey (required)",
        "typ": "radioplayercloud"
    }
}
```

**Radioplayer Unique ID:**

```json
{
    "radioplayer": {
        "rpuid": "--Radioplayer Unique ID",
        "email": "-- email of account (required)",
        "apikey": "-- apikey (required)",
        "typ": "radioplayercloud"
    }
}
```

When using the Radioplayer Unique ID, an additional “territoryid” can be entered if required; by default it is 276 (Germany).

**Old:**

```json
{
    "radioplayer": {
        "url": "https://ingest.radioplayer.de/ingestor/metadata/v1/np/",
        "stationid": "",
        "user": "",
        "pass": "",
        "typ": "radioplayer"
    }
}
```

## Radio.de (radio.net)

```json
{
    "radio.de": {
        "broadcast": "",
        "apikey": "",
        "typ": "radio.de"
    }
}
```

## TuneIn

```json
{
    "tunein": {
        "partnerID": "",
        "partnerKey": "",
        "stationID": "",
        "typ": "tunein"
    }
}
```

## Cover Brands Are Live

```json
{
    "brandsarelive": {
        "id": "1554",
        "default_cover": "https://url.zu.einem.cover",
        "typ": "brandsarelive"
    }
}
```

The name “brandsarelive” is freely definable.

<mark style="color:red;">`id`</mark>

You get the ID for the cover from Brands Are Live.

<mark style="color:red;">`default_cover`</mark>

If no cover data is available, the default cover is sent.

<mark style="color:red;">`typ`</mark>

The type must be “brandsarelive” to send metadata to this provider.

## Icecasts/AIS

```json
{
    "source_icecast": {
        "icecast": "hostname:port",
            "mount": "/mountname",
            "user": "admin",
            "pass": "",
            "typ": "icecast"
    },
    "source_ais": {
        "icecast": "hostname:port",
        "mount": "/mountname",
        "user": "admin",
        "pass": "",
        "typ": "icecast"
    }
}
```

## FTP-Server

```json
{
    "myftpserver1": {
        "channelname": "my audiostream name",
        "host": "myftpserver.io:21",
        "user": "",
        "pass": "",
        "template": "myservice.xml.tmpl",
        "filename": "directory/filename.xml",
        "typ": "ftp"
    }
}
```

<mark style="background-color:blue;">`template`</mark>

template describes the content of filename

## Amqp

```json
{
   "amqp1": {
        "brandid": "",
        "channelkey": "",
        "typ": "amqp"
    }
}
```

{% hint style="info" %}
**Related topics:**

* [Metadata data-set reference](/docs/metadata-data-set-reference/metadata-data-set-reference.md)
* [MetaPort API Specification](/docs/metaport/metaport.md)
* [Metaflow](/docs/platform-description/mediaflow-services.md#metaflow)
  {% 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:

```
GET https://audalaxy.gitbook.io/docs/metaspreader-configuration-settings/metaspreader-configuration-settings.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.