> For the complete documentation index, see [llms.txt](https://docs.revelator.com/pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revelator.com/pro/getting-started/onboarding-to-revelator/migrating-your-catalog/ingesting-your-catalog/delivering-your-catalog.md).

# Delivering via Content Providers (DDEX)

See below for a list of **Supply Chain providers** which deliver DDEX compliant packages. These types of deliveries are the preferred solution if you're  not using the API as it will ensure full product ingestion in a seamless way. 

The following outlines the steps needed in order to deliver your catalog from such providers  to Revelator. 

{% hint style="info" %}
Please share with your Customer Success manager any delivery status information you see along the way
{% endhint %}

### Fuga <a href="#delivering-your-catalog-from-fuga" id="delivering-your-catalog-from-fuga"></a>

1. In your Fuga account, **set up a contract to deliver** your catalog to Revelator
2. Notify Revelator when this is done
3. Revelator will then create a file path folder to accept the delivery, e.g. "`/fuga/rev_customer`"
4. Once the feed and Revelator folder is set up, request to deliver your catalog to Revelator by creating an order for full catalog delivery:

### Consolidated Independent (CI) <a href="#delivering-your-catalog-from-consolidated-independent" id="delivering-your-catalog-from-consolidated-independent"></a>

1. Request to set up a **feed to \*REE\*** from CI
2. Notify Revelator when this is done
3. Revelator will then create a folder to accept the delivery, e.g. "`/ci/rev_customer`"
4. Once the feed and Revelator folder is set up, request to deliver your catalog to Revelator (REE)
5. Create an order for full catalog delivery:

### AudioSalad

1. Contact your AudioSalad Account Manager to open a feed to Revelator
2. AudioSalad will contact Revelator to coordinate and notify you when you can begin your deliveries

### Additional Options for Catalog Migration

#### Sonosuite

* **Request a catalog migration** from within your Sonosuite Dashboard.
* **Fee for exporting** DDEX packages applies.
* **Get SFTP credentials** by contacting Support.
* **Input credentials** into the Catalog Export tool in your SonoSuite Dashboard.

#### Believe

* **Request a DDEX catalog export** from Believe; can be provided to an external storage location (SFTP, AWS).
* **Get our SFTP credentials** from Support and provide these to Believe.

#### Any Other Distributor

* **DDEX export is efficient** as it includes metadata, audio, and cover art files.
* **Request a DDEX export** from your previous distributor, who will need our SFTP credentials.
* **Contact Support** for our SFTP credentials and provide them to your previous distributor.

### **Specifications (FTP Setup)**

Any of the provider you have to be able to undertake this procedure will require from Revelator the following information:

\- IP address of our FTP server: delivery.revelator.com

\- Username: *Provided by our distribution team*

\- Password: *Provided by our distribution team*

\- FTP protocol: FTP

\- FTP port: 221

\- Mode: Passive

\- filepath directory: *Provided by our distribution team*

\- You can add subfolders to your root directory if you would like to segregate catalog coming from separate clients/accounts (if applicable).


---

# 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://docs.revelator.com/pro/getting-started/onboarding-to-revelator/migrating-your-catalog/ingesting-your-catalog/delivering-your-catalog.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.