Skip to main content

MRSS feeds

Updated over a week ago

MRSS (Media RSS) is an extension of RSS that allows publishers to include rich media metadata - such as video - alongside standard feed items. MRSS feeds are commonly used to syndicate video content across multiple services.

Creating a feed

Treefort supports MRSS feeds for video content via our MRSS API endpoint. A GET request to this API endpoint will return an MRSS feed containing any videos in your account that match the provided query parameters. For example the following URL will return an MRSS feed with a channel called "Treefort" that includes all of your videos sorted newest first: https://api.treefortsystems.com/v1/content/mrss?channelTitle=Treefort&orderBy=createdAt_desc

Working with the API

MRSS feeds are supported via a Treefort API endpoint. If you haven't worked with our API before, read the Treefort API guide. You must call the MRSS feed endpoint like any other API endpoint (e.g. don’t forget to provide the X-Treefort-Tenant and Authorization headers).

Security

A Treefort MRSS feed will contain signed URLs to source media for any videos in the feed. This means that anyone with access to an MRSS feed has access to stream and download all of the videos in the feed. To prevent unwanted access to your media, our MRSS feed API endpoint requires authentication for help authenticating your requests (see “Working with the API” above). The signed URLs in each MRSS feed are valid for 14 days. If another service caches these URLs, make sure it re-fetches them from the feed at least every 14 days.

Basic auth

In some scenarios the standard two-step OAuth client credentials grant used to authenticate API requests is not practicial for MRSS access. For example you may be working with a third party service that can only make a single GET request to fetch an MRSS feed. To accomodate this use-case our MRSS API endpoint also supports Basic auth - just pass your API client ID as the username and your API client secret as the password along with your GET request to the MRSS endpoint.

⚠️ We only recommend using Basic auth when absolutely necessary. Your client secret is extremely sensitive and passing it with every API request is not ideal.

Did this answer your question?