Skip to main content
To keep the Titan OS metadata library accurate and up to date, we require a reliable method of accessing your content feed. We support multiple delivery methods and formats, but prioritize solutions that provide high availability and support secure, automated access. Once your feed is ready, submit its URL, market coverage, authentication details, and any supporting materials through the Titan OS Partner Portal. Authentication credentials must be submitted through the Partner Portal and should not be shared by email. For step-by-step instructions, see Submit Metadata Feeds.

​
Accepted formats

  • Feeds built on the Titan Schema Feed Format (see Feed Setup) must be delivered as JSON. XML is not accepted for the Titan Schema.
  • Feeds in a partner’s own or custom format may be delivered as either JSON or XML. JSON is strongly preferred for efficiency and ease of mapping.

​
Preferred method: API endpoint

Our preferred delivery method is a standard REST API endpoint. This allows the Titan OS ingestion service to retrieve updates automatically on a scheduled basis.
  • Authentication: Supported authentication methods include Basic Auth, API keys, and bearer tokens. Enter the applicable credentials securely in the Partner Portal.
  • Access requirements: The endpoint must be reachable by Titan OS without IP allowlisting. It may - and should, where appropriate - be protected using one of the supported authentication methods.
  • Payload structure: A one-request model is preferred. All metadata for a title, including descriptions, artwork, deeplinks, and availability, should be included in the same response.

​
Alternative: hosted file

If an API endpoint is not available, Titan OS can retrieve a static feed file from a partner-hosted server.
  • Stable URL: The file must remain available at a consistent HTTPS URL so that the ingestion service can retrieve it during each synchronization.
  • Authentication: If the file is protected, provide the required authentication details through the Partner Portal.
  • Timeline: A file-based configuration may require additional setup and can extend the integration timeline.

​
Alternative: S3 bucket

If an API endpoint or a partner-hosted file is not available, Titan OS can retrieve your feed from an Amazon S3 bucket.
  • Access: The partner must add Titan OS’s ARNs to the bucket’s access policy so the ingestion service can read the feed. ARNs are provided through the Partner Portal during onboarding.
  • Stable path: The object key must remain consistent so the ingestion service can retrieve it during each synchronization.
  • Timeline: A bucket-based configuration may require additional setup and can extend the integration timeline.

​
Feed structure requirements

To optimize the intake process, follow these structural guidelines for your feed: