> ## Documentation Index > Fetch the complete documentation index at: https://docs.titanos.tv/llms.txt > Use this file to discover all available pages before exploring further. # Submit Metadata Feeds App partners can submit, configure, and manage their catalogue and recommendation feeds through the [Titan OS Partner Portal](https://partners.titanos.tv). The Partner Portal provides a secure, guided workflow for submitting feed URLs, authentication credentials, market configurations, and supporting materials. It also allows you to track each feed from its initial submission until it becomes **Live**. ## Before you begin Before submitting a metadata feed: * Your app must already exist in the Partner Portal. * Your feed must be available through a stable HTTPS URL. * Review the supported [Feed Delivery & Access Methods](feed-delivery-access-methods.md). * Review the technical requirements in [Feed Setup](https://docs.titanos.tv/metadata-feed-setup). * Make sure you have the necessary authentication credentials if the feed is protected. ## Submit a catalogue feed 1. Sign in to the [Titan OS Partner Portal](https://partners.titanos.tv). 2. Open the relevant app. 3. Navigate to **Metadata Feeds**. 4. Select the option to add a catalogue feed. 5. Enter the feed URL. 6. Select the markets covered by the feed. 7. Add authentication details if the feed is protected. 8. Add any supporting materials or additional access information. 9. Review the configuration and submit the feed. You can save the submission as a draft and return to it before submitting it for review. ## Configure markets Select the markets covered by the catalogue feed. * If the feed applies to all supported app markets, select **All app markets**. When **All app markets** is selected, individual markets do not need to be added. * If the feed only applies to specific markets, select each applicable market individually. The market configuration should match the availability and deeplink information contained in the feed. ## Configure authentication If the feed is protected, select the applicable authentication method and provide the required credentials. Supported authentication options include: * Basic Auth * API key * Bearer token Credentials are stored securely and used only to access and process the submitted feed. Do not provide feed credentials by email. If Titan OS requires additional instructions to access the feed, include them in the additional information field or as supporting material. ## Add supporting materials Supporting materials can be provided to help Titan OS understand, validate, or integrate the feed. Examples include: * Feed specifications * Field-mapping documentation * Sample payloads * Authentication instructions * Market-specific implementation notes Only provide materials relevant to the submitted feed. ## Configure recommendations During the submission process, choose how recommendations should be generated. ### Partner-managed recommendations Select this option if you want to provide ranked content selections through your own recommendation feed. The recommendation feed: * Is submitted separately from the catalogue feed * Must reference content IDs included in the catalogue feed * Can only cover markets included in the catalogue feed * Is reviewed and moved to **Live** independently See [Recommendations](https://docs.titanos.tv/metadata-feed-setup#recommendations) for the required structure. ### Titan OS-generated recommendations Select this option if you want Titan OS to generate recommendation rows using the content available in your catalogue feed and relevant platform signals. A separate recommendation feed is not required when this option is selected. ## Review process After submission, Titan OS reviews the feed configuration and supporting information. The review includes: * Feed accessibility * Authentication * Market configuration * Feed structure * Supporting materials * Recommendation configuration Submitting a feed does not make it immediately available to users. The feed must first be reviewed, integrated, and approved by Titan OS. ## Feed statuses The current status of each feed is shown in the Partner Portal. | Status | Meaning | | :- | :- | | **Draft** | The feed has been saved but has not yet been submitted. | | **Submitted** | The feed has been submitted to Titan OS. | | **In progress** | Titan OS is reviewing or integrating the feed. | | **Revision needed** | The partner must correct or complete the submitted information. | | **Live** | The feed has been successfully integrated and activated. | ## Revision needed If Titan OS cannot continue with the submitted information, the feed will be returned with the status **Revision needed**. You will receive an email notification when a revision is required. The revision details and requested changes are available within the Partner Portal. To submit a revision: 1. Open the affected feed in the Partner Portal. 2. Review the revision information. 3. Update the feed configuration or supporting information. 4. Resubmit the feed for review. ## When a feed becomes Live You will receive an email when a feed has been successfully integrated and moved to **Live**. Catalogue and recommendation feeds are reviewed independently. Your catalogue feed may therefore be **Live** while the recommendation feed is still being processed. The Partner Portal is the source of truth for the current status of each feed. ## Update a feed Changes to a submitted or **Live** feed should be made carefully, as they may affect the active metadata integration. If you need to update a feed URL, authentication details, market coverage, supporting information, or recommendation configuration, open the feed in the Partner Portal to see the available actions. Changes may require an additional review before they are applied to the live integration. Contact the Titan OS team before making structural changes to a **Live** feed or if the required information cannot be updated through the Partner Portal. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.