FastPix delivers consistent branding and higher viewer engagement by prepending and appending intro and outro segments to any on-demand video using introUrl and outroUrl fields in the create request, which produces a single merged asset with its own mediaId and playbackId. Add these fields at upload time for new media, or reference an existing mediaId to attach segments to content already in your library.
mediaId: the unique identifier FastPix assigns to every uploaded asset. FastPix generates a new mediaId each time you attach an intro or outro, even when the base video is existing media.playbackId: the access-controlled identifier used to build the HLS playback URL at https://stream.fastpix.com/<playbackId>.m3u8.accessPolicy: controls who can play the asset. Accepted values are public and private.introUrl / outroUrl: URLs of the segments FastPix prepends and appends to the base video during transcoding.Use the Create media from URL or Upload media from device endpoint. Attach one or both segments on the same request that creates the asset.
Gather the URLs for the following files:
NOTE
Each source file must be encode-ready. Source quality determines the quality of every rendition FastPix generates.
In the request body, set:
url to the base video URL.introUrl to the intro video URL (optional).outroUrl to the outro video URL (optional).Important
Replace each URL in the examples with the actual path to your media files.
To add an intro and outro from the dashboard, you need to:
introUrl and outroUrl fields in the JSON configuration.introUrl and outroUrl values with the public URLs of your intro and outro videos.Call the Create media from URL endpoint and reference the existing mediaId in the url field.
NOTE
FastPix always creates a new asset when you attach an intro or outro to existing media. The original asset is unchanged.
url to fp_mediaId://{Media_Id} using the mediaId of the existing asset.introUrl to the intro URL.outroUrl to the outro URL.Replace introUrl and outroUrl with the actual paths to your media files.
FastPix emits dedicated webhook events when each segment finishes transcoding:
video.media.intro.ready: triggered when the intro has been added.video.media.outro.ready: triggered when the outro has been added.What happens if the intro or outro frame rate differs from the base video?
FastPix requires the frame rates to match. If they do not, the transcode fails or produces unstable output. Re-encode the intro or outro to match the base video frame rate before retrying.
Can I reuse the same intro and outro across many videos for branding automation?
Yes. Host the intro and outro on a stable URL and reference the same introUrl and outroUrl in every create-media request. This is the recommended pattern for branded intro outro reuse across a catalog.
Does attaching an intro or outro to existing media modify the original asset?
No. FastPix creates a new mediaId and playbackId for the combined output. The original asset remains unchanged and accessible under its original mediaId.
Why do I need separate webhooks for video.media.intro.ready and video.media.outro.ready?
FastPix encodes and attaches each segment independently, so each emits its own event. Wait for both events (when both segments are supplied) before treating the merged asset as complete.
Can I apply intros and outros in bulk?
Yes. Loop the Create media from URL endpoint over your source list and pass the same introUrl and outroUrl in every request. This is the programmatic equivalent of an intro outro maker for your catalog.