Syndication

Syndication allows you to push live channels, virtual linear channels, and live events to external platforms such as YouTube, Facebook, Twitch, or FAST platforms like Pluto TV, NewsOn, etc.

While Uplynk’s primary delivery path is designed for distribution - Syndication is optimized for contribution, allowing you to to feed downstream systems and easily meet their requirements.

Syndication supports:

• Delivery via RTMP, RTMPS, SRT, RIST, Zixi, HLS-Pull, and HLS-Push.
• SCTE-35 for ad signaling and automation.
• Contribution to platforms and partners that require unencrypted streams.

How It Works

At its core, Syndication is made up of two key components: targets and jobs.

• A target defines where content should be sent and how to reach that destination (e.g., YouTube via RTMP, AWS MediaConnect via Zixi).
• A job is a live connection that sends content from a channel or event to a target.

You create a target once and configure it with everything needed to syndicate to that destination. Then, you create one or more jobs from that target, each job linked to a specific Uplynk channel or live event.

This structure allows you to:

• Reuse the same target across many jobs.
• Maintain consistency through shared templates.
• Adjust individual jobs as needed without affecting others.

Example: You might have one YouTube target and create five different jobs from it—each one linked to a different channel or event.

🚧

Only one job can be active at a time per target.

This is because the target contains the connection details (such as a stream key or ingest URL). Multiple jobs attempting to use the same target simultaneously would result in connection conflicts. To push different content to the same destination at different times, stagger the jobs or use separate targets.

Syndication is designed to be flexible and scalable, especially for workflows like FAST, where content needs to be sent to multiple endpoints reliably and repeatedly.