Introduction

Feed Clips is the only music API that lets you legally integrate premium, licensed song clips from major-label and independent artists into short-form content. Built for teams that need to move fast, Clips delivers curated, cleared music clips designed for UGC formats like stories, posts, reels, cards, and greetings. 

With Feed Clips, you can launch engaging music features quickly without the legal and operational hurdles of custom licensing. Our API and Clips Studio give you everything you need to deliver the music that your users know and love. 

Our goal at Feed is to help your team harness the power of music to boost engagement, increase conversion, and retention. We fuel creators with trend-ready clips made for easy edits, emotional impact, and shareable short-form content. Feed simplifies compliance by handling all licensing, royalties, and rights holder reporting, while our plug-and-play API lets you fast-track integration and get live with music in days, not weeks.

What you’ll learn 

• How it works: Core use cases, integration flows, and reporting requirements.
• Feed Clips Studio: Preview the catalog, access developer resources, and review analytics. 
• User experience: Best practices for surfacing music in your app to maximize adoption.
• Requirements and restrictions: Quick reference for compliance and design guardrails.
• Content ID: How to implement audio fingerprinting to safeguard user uploads.
• Why licensing matters: How Feed.fm makes it easy, and what you need to know. 

⭐️ Before diving in, make sure your team has reviewed the Terms & Conditions, received access to the Clips Studio, and defined a clear use case for integrating Feed Clips.

Questions? The Feed Clips team is here for you every step of the way! Get in touch.

Feed Clips API: How it works

The Feed Clips API provides access to licensed music clips for use in your app. Content is organized by collections, which group tracks by genre, theme, mood, decades, and season. Collections are the primary way for your users to browse and discover music. 

Feed Clips offers two types of music clips:

Curated clips are pre-made, ready-to-use clips created by Feed.fm’s curation team. Each curated clip highlights the most representative portion of a song, making them ideal for fast, seamless integration. Consider starting with curated clips as your default implementation. 

Custom clips are clips created by your users from full-length tracks. Custom clips may be up to 60 seconds maximum. Your app will provide a clip selector UI, and the Feed Clips API will return a clip ID and signed URL for playback. See the Clips Workflows section below for more details. 

Both curated clips and custom clips may be streamed directly or synced with user-generated content, animations, or templates.

Accessing collections

Collections are the foundation of the Feed Clips library. Collections are accessed through the API using collection IDs, which you’ll find in Clips Studio. You can copy all collection IDs at once or select individual IDs to associate with your app. 

The user experience (UX) for browsing and previewing collections is entirely up to you. This flexibility is intentional to provide you with a seamless fit that lets you design a browsing experience that feels native to your app's design and community. You have complete creative freedom—whether your app uses swiping, scrolling, or grid layouts, you decide how music is presented. By controlling the look and feel, you ensure music browsing enhances your brand authenticity rather than feeling bolted on.

Later in this guide, we’ll share extensive examples and best practices for User Experience. We encourage you to adapt the user experience for engaging with collections in a way that feels natural for your product and audience.

Common use cases

The Feed Clips API is designed to support a variety of user experiences. Here are the most common ways customers integrate Feed Clips into their apps:

• Browse all collections: Surface all the full collections, allowing your users to have access to the full depth and breadth of the Feed Clips catalog.

• Callout specific collections: Surface specific collections within your user experience. This can be a great way to highlight trending or seasonal collections to drive user engagement. 
• Grab specific clips by ID: Request an individual clip directly using the clip ID to integrate specific clips into your product. This may be done with curated clips or custom clips.

Reporting

Accurate reporting is required for compliance with rightsholders and is a core piece of your integration. Feed.fm must coordinate a review of your app once all reporting endpoints have been integrated to ensure proper setup before launch. This is a critical step to ensure compliance with our music licensors.

Your app must track and send the following events to Feed.fm using the provided endpoints: 

• App open: Sent when a user opens your application (/app-start).
• App close: Sent when a user closes your application (/app-close).
• Play: Sent whenever a clip begins playback, including previews and plays of UGC containing a clip (/play).
• Track play: Sent whenever a full-length track begins playback during custom clip creation (/track-play).
• Add: Sent when a user confirms selection of a clip for their content (/add).
• Share: Sent when a user shares content containing a clip to an approved third-party platform (/share).
• Download: Sent when a user downloads synced content to their device (/download).

Both curated clips and custom clips require event tracking across this full set of endpoints. These reporting requirements are not options. They are a core part of your compliance with licensing terms and serve as the means for reporting music engagement metrics to you in Clips Studio.

Read on for a full list of requirements and restrictions.

Curated clips workflow

Custom clips workflow

Non-playable clips

From time-to-time, rights to certain tracks may expire or be restricted. To stay compliant, your app must verify playability for every clip before playback. We make this simple using the /music-check endpoint. How this works:

• Collections: If a track is no longer playable, it will automatically be removed from collections returned by the API.

• Streaming: If a user attempts to play a clip of a song that no longer has rights, /music-check will return the clip Id for the songs that are no longer available in the response. 
• Synced media: For content that has already been created with a clip, your app is responsible for blocking playback if the /music-check endpoint returns a “not playable” response. 

See the user experience section of this guide where we share examples and best practices to help you address non-playable clips, ensuring your users have a seamless experience. 

User experience

The Feed Clips API is designed to be flexible so you can create a music experience that feels authentic to your product. While Feed.fm provides the licensed catalog and technical framework, your team controls how users browse, preview, stream, and sync music within your app. 

To support you with design, this guide will cover all the primary user interactions for Feed Clips including examples and best practices to help you design a seamless and engaging user experience. 

• Browsing collections
• Previewing and selecting curated clips
• Creating custom clips
• Syncing music to media
• Handling non-playable clips
• Sharing and downloading
• Georestrictions

Browsing Collections

Collections are the foundation of the Feed Clips experience. How you present them to your users should make discovery feel exciting, intuitive, and natural within your app. 

There are several approaches you can take when surfacing collections. Here are some examples:

Carousels: Present collections in a horizontal carousel that users can swipe through. This can be oriented at the category level (genres, moods, themes, etc) or can include specific collections (pop, hip-hop, dance, rock, etc). This works well for quick browsing and keeps the UI lightweight.

Category tabs or sections: Organize collections into categories such as genres, themes, vibes & moods, seasonal, artists. This approach is helpful when you want to surface the full depth and breadth of the Feed Clips catalog. 

Grid layouts: Show multiple collections at once in a grid view using the collection art provided (or your own art). Grids allow for visual variety and make it easy to highlight featured content. 

Spotlights and featured collections: Highlight a single collection, such as Halloween or Love Songs to align with current events or seasonal campaigns. 

Grouping Collections by category

You can create your own categories for collections to help organize your user experience. Some ideas include:

• Genres
• Themes
• Vibes & moods
• Artist collections
• Seasonal favorites
• Decades

By grouping collections, you give users multiple ways to engage. The more intuitive and flexible your browsing options, the more likely users are to find and use clips that feel right for them. 

Previewing and selecting Curated Clips

Curated clips are designed to make the music selection fast and intuitive. Your users should be able to quickly hear a snippet, get the context they need, and then easily confirm their choice.

Best practices for previewing

• Quick play access: Use a visible play button or tap gesture so users can preview without extra steps.

• Contextual information: Show track title, artist name, release title, and album art with each preview so users can easily identify the music they’re choosing. 
• Consistent playback controls: Offer familiar controls (play/pause toggle, progress indicator) to minimize confusion. 
  
  

Best practices for selection

• One-tap confirmation: Minimize steps between previewing and selecting to encourage usage. 

• Highlight selected state: Once a clip is chosen, show a confirmation state (ie. checkmark or highlight) so users know it’s been applied. 

• Encourage exploration: Don’t lock users into one preview-to-selection flow. Allow them to explore multiple clips freely. 

Creating custom clips

Custom clipping gives your users more creative control by allowing them to choose the exact portion of the track they want to use. To make this process intuitive, your app should provide a smooth preview experience, an easy-to-use selector, and clear confirmation once a clip is created. 

Best practices for previewing clips within a collection are the same as above. However, once the user has selected a track, they should transition to the selector where they can audition and select their custom clips. 

Auditioning custom clips

• Audition in segments: Users may only preview 60 seconds of a track at a time (per licensing requirements). 

• Default to curated clip timestamps: To reduce effort, initialize the selector at the start and end points of the curated clip for the track (provided by the Feed Clips API). This will land users in the most familiar region of the track rather than starting at the beginning. 
• Contextual metadata: Keep artist name, track title, release title, and album art visible while users are previewing so they always know what they’re clipping. 
  
  

Clip selector interface

• Start/end handles: Provide draggable handles on a scrubber to let users define their start and end times. 

• Visual feedback: Highlight the selected portion clearly (ie. shaded region) so users can see clip boundaries. 
• Enforce limits: The UI must restrict selections to a maximum of 60 seconds. Feed does not enforce a minimum duration for a clip, consider implementing a practical floor to ensure the user experience feels intentional.  
  
  

Finalizing a custom clip

• Immediate preview: Allow users to play back their chosen segment instantly before saving. 
• Confirm action: Provide a clear call to action such as “save”.

Syncing music to media

Syncing is where users see their creativity come to life, combining their chosen clip with video, images, or templates. While the Feed Clips API doesn’t provide syncing services, we have outlined some best practices. A thoughtful UX here ensures the process feels seamless and rewarding. 

Best Practices for Syncing

• Simple flow: The moment a user selects a clip, they should clearly understand how to add it to their video or creative asset. 

• Automatic alignment: Wherever possible, auto-align clips to the start of the video so users don’t need to worry about timing unless they want to. 

• Preview experience: Always provide a full preview before saving or sharing. This helps users confirm that audio and video are aligned as intended. 

• Playback controls: Include familiar play/pause and scrub features so users can quickly recheck their sync.
• Muxing behind the scenes: Keep the technical process invisible. Users should feel like adding music happens instantly. 
  
  

Optional Enhancements

• Start-time adjustments: Let advanced users shift where the clip starts in relation to their video.

• Looping (if prior approval has been granted): If looping is permitted, allow users to enable looping the music clip for videos longer than 1 minute (the max allowable clip length). 

• Templates and effects: Encourage creativity by pairing synced clips with templates, text, or filters. 

Handling non-playable clips

From time to time, certain tracks may become unavailable due to changes in music licensing rights. We call these non-playable clips. When this happens, the track can no longer be streamed, played as synced media, or included in new user-generated content. 

Because availability can change, your app must check playability before playback and provide a smooth, user-friendly experience when a clip is unavailable. The goal is to prevent silent failures and guide listeners forward in the user experience. 

• Collections: Non-playable clips will be automatically removed from collections, so users cannot select or sync clips that have already lost rights. 
• Streamed media: If you’ve programmed a clip to stream in your app consider a default user message such as “this clip is no longer available”. Additionally, it is recommended that you replace the unavailable clip with another option from the catalog. 

• Synced media: If synced media returns a non-playable message, playback must be blocked. Consider displaying a clear message such as “the audio is no longer available for this video”. 

• For creators: Some apps offer creators the option to re-sync a new clip to existing content. This can be technically complex, and many platforms simply require the creator to remove the video. If re-syncing is supported, each new sync event must be tracked. Consider your product’s resources and workflows before implementing re-syncing. 

Sharing and downloading

Sharing and downloading are key ways your users can extend the impact of their creations. Both require accurate reporting to Feed.fm for compliance with rights holders, and both should be presented to users in a way that feels natural to your app. 

Downloading

Users may download synced media with Feed Clips to their device for personal use only. UX best practices are as follows:

• Offer a clear download button or option
• Confirm successful downloads with a message like “Saved to your device”
• If a download fails, provide a retry option

Sharing

Users may share synced media to approved third-party platforms. Approved platforms are determined during the contracting process. If you have any questions about this please contact your customer experience manager. UX best practices are as follows: 

• Use the device’s native share sheet where possible for a familiar experience
• Clearly display the supported platforms
• If a platform is not approved, don’t display it as an option in your share UI
• Provide users with a confirmation message like “Shared successfully”
• Ensure consistent placement of share/download options across your app to build user confidence

Georestrictions

Feed Clips is currently licensed for use in the United States (and its territories) only. If a user outside the US attempts to access Feed Clips music through your app, the API call will be denied. 

UX Best Practices

• Clear messaging: Display a straightforward message such as: “Music is not available in your region”.

• Consistent treatment: Apply the same message across browsing, playback, and synced content so users don’t encounter different error states. 
• Fallback UX: Consider hiding Feed Clips features entirely for users outside the US once the restriction is detected, instead of surfacing repeated errors. 

Requirements and Restrictions

The Feed Clips API gives you the flexibility to design a music experience that fits your app, but there are specific requirements and restrictions that must be followed to ensure compliance with licensing terms. These rules protect artists, rights holders, and your business, while also ensuring a consistent user experience for your audience. 

This section outlines what you must do (requirements) and the limits you must design for (restrictions). Feed will review your app prior to launch to confirm these are implemented correctly. 

Remember, your Feed.fm customer experience team is here to help! Please reach out with questions, concerns, or clarifications. 

Requirements (must do)

Please ensure you have fully reviewed Feed Clip’s Terms and Conditions. This document is a quick reference, but does not replace the terms and conditions for which you are responsible. 

These are compliance-critical and required for every Feed Clips integration: 

• End User Licensing Agreement (EULA): The Feed Clips EULA must be included in your app’s terms and conditions. 
  • We’ve created a template for you here.

• Attribution and notices: Your app must display attribution information exactly as provided by Feed.fm, including:

• Song title
• Album name
• Artist name
• Event reporting: All required events must be tracked via Feed.fm’s endpoints:
  • /app-start: Sent when a user opens the app.
  • /app-close: Sent when a user closes the app.
  • /play: Sent whenever a clip begins playback (including previews and synced media).
  • /track-play: Sent when a full-length track begins playback during custom clip creation.
  • /add: Sent when a user confirms selection of a clip for their content.
  • /share: Sent when content containing a clip is shared to an approved third-party platform.
  • /download: Sent when synced content is downloaded to a device.
• Both clip types: Reporting applies equally to curated clips and custom clips. Every play, sync, share, and download must be reported.
• Playability checks: Every clip must be checked for rights availability using the /music-check endpoint before playback.
• Credential use: Production credentials must be used for live, in-market apps. Development credentials are for staging and testing only.
• Approved platforms only: Sharing options may only include third-party platforms that have been pre-approved and detailed in your contract.
• Personal use downloads: All downloads of synced media must be for personal use only.

Restrictions (limits you must design around)

These are technical or licensing constraints built into the Feed Clips system. Apps must not override or work around these rules.

• Audio quality & security: Streams must not exceed AAC 256 kbps or MP3 320 kbps and must implement anti-copy measures.
• Security solutions: Apps must comply with rights holders’ technical requirements including device authentication, geo-filtering, encryption, and anti-circumvention measures (see terms and conditions for full details).
• Custom Clip length: Custom clips cannot exceed 60 seconds. You may enforce a shorter limit (e.g., 30 seconds) if desired, but users must be clearly notified of the maximum length allowed.
• Custom clipping behavior: While your app has access to the full track during custom clip creation, users may not listen to the full track uninterrupted. Tracks must only be auditioned via your custom clipping interface (scrubber). Users may only preview up to 60 seconds of a track at a time when auditioning custom clips. 
• Clip stacking: Users may not add more than one clip to a single piece of media. Stitching together multiple clips or attempting to recreate a full track is not allowed.
• Signed URL expiration: Signed URLs for audio are valid for 24 hours. Cached files must be refreshed after this period.
• Non-playable clips: Clips may lose rights at any time.
  • In collections, they will automatically be removed.
  • For streamed or synced content, playback must be blocked if /music-check returns “not playable.”
• Georestrictions: The Feed Clips API is accessible only in the United States and its territories. Calls from outside the US will be denied. Apps should provide an error message to users who encounter this limitation.
• Creation of derivative works: Clips cannot be remixed or altered in any way without express permission from Feed.
• Looping: Looping is only allowed with prior approval at contract.
  • Looping must be implemented using the curated clip or custom clip provided.
  • Each loop counts as an additional /play event and must be tracked.

Content ID

Any app that allows users to upload their own content must implement Content ID to ensure compliance with music licensing rights. Content ID verifies whether user-uploaded media contains unlicensed or unidentifiable music, and ensures that only content including approved Feed Clips music may be used. 

Feed.fm has selected ACRCloud as our approved provider for this service. All customers enabling user generated content uploads must contract directly with ACRCloud. 

How Content ID works

1. When a user uploads media, the ACRCloud SDK embedded in your app generates an audio fingerprint of the media.
2. Your app passes that fingerprint to Feed.fm.
3. Feed.fm passes the fingerprint to ACRCloud to identify the track. 
4. Feed.fm checks the track against the Clips library:
   1. If the track is licensed the upload may proceed
   2. If the track is unlicensed or unidentifiable, the upload must be blocked entirely or the audio must be stripped before the upload can proceed. 
      
      

Customer responsibilities

• Contracting: You will contract directly with ACRCloud for use of their SDK. Feed.fm can liaise during setup, but the financial and contractual responsibility rests with you.
• Implementation: You will implement the ACRCloud SDK into your app, which will generate audio fingerprints.
• Credential Sharing: Your ACRCloud credentials must be provided to Feed.fm via the Clips Studio API page. This will allow Feed.fm to send the fingerprint to ACRCloud for music identification purposes in order to reference it against the Feed Clips catalog.
• Compliance: It is your responsibility to ensure that no unlicensed audio passes through to end-users. 

Handling Non-Compliant Media

If Content ID identifies non-compliant audio (music not licensed by Feed.fm), you have two options:

1. Block the Upload: Display an error message and prevent the video from being uploaded. This is the minimum requirement. 
2. Strip the Audio: Remove background audio from the video entirely and allow the user to proceed with their video using only licensed clips (Note: This capability must be implemented by your team. Feed.fm does not provide audio-stripping tools). 

UX considerations

How you handle Content ID rejections will directly impact the user experience. By implementing some best practices, you can ensure the user experience is smooth and as painless as possible. 

Best practices at upload

• Proactively provide guidance during recording or upload to reduce the risk of rejection:
  • Encourage users to record in quiet spaces
  • Recommend using headphones with a noise cancelling microphone to avoid capturing background audio
  • Remind users not to sync music to media before uploading
    
    

When unlicensed audio is detected

• Clear messaging: Show a message such as: “We’ve detected background music in your video that isn’t available for use. Please remove the audio or record again.”

• Offer options: Depending on your implementation, you may:

• • Block the upload and provide retry guidance
  • Strip the audio automatically and allow the user to continue with Feed Clips music
  • Do not allow users to bypass or ignore a content ID rejection
• Encourage next steps: Provide an easy path forward so users don’t feel stuck. 

Music licensing and compliance

Why licensing matters

Whether music becomes part of your product experience through short-form clips, livestreams, or any kind of UGC, proper licensing is essential. It protects your business, your users, and the artists who make your platform possible. Unlicensed music use can result in content takedowns, copyright claims, or even lawsuits, all of which can erode user trust and stall your growth.

Consumer APIs like Spotify, Apple Music, or YouTube are built for personal listening, not app integrations. Using them within your platform violates their terms and copyright law.

How Feed.fm keeps you covered

With Feed.fm, all licensing, reporting, and compliance are managed for you, ensuring every track is rights-cleared and accounted for. 

Compliance also requires partnership. Apps must follow Feed.fm’s integration requirements, including proper attribution in UX design and accurate event tracking using our provided endpoints.

⭐ Please revisit the requirements and restrictions section for a complete list of compliance-critical provisions.

With Feed Clips, you get a fully licensed, curated, and compliant music experience built for social and UGC platforms. Feed.fm handles the complexities of rights management and reporting, while your team ensures accurate implementation and attribution. Together, we deliver a seamless, compliant experience for your users and the artists behind the music.