# Create Catalog

## Create Catalog

<mark style="color:green;">`POST`</mark>`/catalog/create`

As the first stage of the distribution process, you need to create a catalog. In this documentation, we will provide detailed information for catalog creation.

**Headers**

| Name          | Value              |
| ------------- | ------------------ |
| Content-Type  | `application/json` |
| Authorization | `Bearer <token>`   |

**Body**

<table><thead><tr><th width="237">Name</th><th width="130">Type/Values</th><th width="157" data-type="checkbox">Mandatory field</th><th>Description</th></tr></thead><tbody><tr><td>MainArtist</td><td>string</td><td>true</td><td>If the catalog artists are more than one, you can add more artists by separating them with “,”.</td></tr><tr><td>Feat</td><td>string</td><td>false</td><td>If you have more than one featured artist in your catalog, you can add more artists by separating them with “,”.</td></tr><tr><td>CatalogTitle</td><td>string</td><td>true</td><td>The catalog name must not use special characters and must comply with platform rules.</td></tr><tr><td>Type</td><td>['EP', 'Single', 'Albüm']</td><td>true</td><td>Choose a suitable type according to the content of your catalog.</td></tr><tr><td>Label</td><td>string</td><td>true</td><td>Type the name of the <a href="/pages/Z6rUHjvZ5lpO9VGICbXt">label you have access to.</a></td></tr><tr><td>Genre1</td><td>string</td><td>false</td><td>Select the right <a href="/pages/HzyhymK7vPHHsqaiQviw">genre</a> for your catalog.</td></tr><tr><td>Genre2</td><td>string</td><td>false</td><td>Select <a href="/pages/HzyhymK7vPHHsqaiQviw">genre</a> 2 for your catalog if you want.</td></tr><tr><td>CLine</td><td>string</td><td>false</td><td>Add Copyright line for your catalog.</td></tr><tr><td>PLine</td><td>string</td><td>false</td><td>Add Phonographic copyright line for your catalog.</td></tr><tr><td>ReleaseDate</td><td>date (yyyy-mm-dd) </td><td>false</td><td>Set a release date for your catalog.</td></tr><tr><td>UPC</td><td>integer</td><td>false</td><td>You can add your UPC or EAN codes in this field. If left blank, it will be created automatically by the system.</td></tr><tr><td>CatalogNo</td><td>string</td><td>false</td><td>You can use this field if you are using a special numbering for the catalog. If left blank, it will be created automatically by the system.</td></tr><tr><td>CatalogVersion</td><td>string</td><td>false</td><td>You can use this field if your catalog has a special name or a special version. (Remix Version, Slowed-Reverb etc.)</td></tr><tr><td>Platforms</td><td>string</td><td>false</td><td>Add the <a href="/pages/pQrmZxdzrUlZIkYUaw2l">platforms you are authorized</a> to distribute to, separated by “,”. Only Platform ID's should be added.</td></tr><tr><td>Territories</td><td>string</td><td>false</td><td>Add in which territories your catalog should be available. <a href="/pages/CHrGB3R0jmHPtRpJJ1HG">Territories</a> can be separated by “,”. If all regions are available, they should be added as “WW”.</td></tr><tr><td>ArtistMapping</td><td>array</td><td>false</td><td>For delivery to the correct profiles.</td></tr></tbody></table>

> ```php
> //ArtistMapping (PHP)
>
> $input['ArtistMapping'] = [
>     'MainArtist' => [
>         1 => [
>             'Spotify' => 'Artist1 Spotify Profile Link',
>             'AppleMusic' => 'Artist1 Apple Music Profile Link'
>         ],
>         2 => [
>             'Spotify' => 'Artist2 Spotify Profile Link',
>             'AppleMusic' => 'NEW' //Create a new profile for Apple Music
>         ]
>         
>         ...
>         
>     ],
>     'Feat' => [
>         1 => [
>             'Spotify' => 'FeatArtist1 Spotify Profile Link',
>             'AppleMusic' => '' // If empty, the DSP matches the profile itself
>         ]
>     ]
> ];
> ```

{% hint style="info" %}
The values required for API are listed. Just adding these values is not enough for distribution. You may also need to add the following values for distribution. In this way, you do not need to edit the catalogue again.

* MainArtist
* CatalogTitle
* Type
* Genre1
* Label
* CLine
* PLine
* ReleaseDate
* Platforms
* Territories
  {% endhint %}

**Response**

{% tabs %}
{% tab title="200" %}

```json
{
    "success": "true",
    "data": {
        "CatalogUnique": "QnJlbWl1bSBOZXR3b3Jr=",
        "Message": "Katalog başarıyla oluşturuldu."
    }
}
```

{% endtab %}

{% tab title="403" %}

```json
{
  "success": "false",
  "data": "Forbidden"
}
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions: 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://developer.bremium.network/api-sections/catalog/create-catalog.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.