Skip to main content

Welcome to Feed Clips

Updated Sep 24th, 2025

Welcome to the documentation for the Feed Clips API. This guide will walk you through everything you need to know to integrate our licensed music library into your application.

Introduction to Feed Clips​

Feed Clips is a popular music API that allows you to incorporate short, licensed music clips into your users' content. Feed Clips is a RESTful API that's used to preview our catalog, request music clips, create custom music clips from our catalog, report usage events, and more.

How It Works​

  1. Choose a Clip: browse our Clip Collections for the right song. The best section is selected by default, or select any 60 second section of the song that you want.
  2. Request a Clip: Your application requests a music clip from our API.
  3. Receive a Signed URL: We return a secure, signed URL for the audio file. This URL is valid for 24 hours.
  4. Download and Cache: You download the audio file and cache it on your servers for up to 24 hours.
  5. Sync with Content: You can then mux the downloaded audio with user-generated video, animations, or other creative content.
  6. Track Everything: You are required to send event data back to us for every key user interaction for two reasons:
    1. Ensuring artists and rights holders are properly compensated.
    2. Enabling music engagement insights that we provide you in Clips Studio.

Getting Started​

1. Sign into Clips Studio​

Before you can start, you will need to create an account for Clips Studio. This is where you can browse through Collections, manage your account, view analytics, find your API credentials, and access this documentation.

2. Authentication​

The Feed Clips API uses a token-based authentication system. All API requests must be made over HTTPS and include an Authorization header with your API token.

To get your token, you must first authenticate with your token and secret using the base URL of https://api.clips.feed.fm. Your API credentials can be found on the API page of Clips Studio.

Note: All API requests also require a clientId parameter in the request body. This identifies the end user making the request and must be consistent across devices and sessions. See Client ID for detailed requirements.

POST /authenticate

Request Body:

{  
  "token": "YOUR_CLIENT_TOKEN",  
  "secret": "YOUR_CLIENT_SECRET"  
}

Response:

{  
  "token": "YOUR_BEARER_TOKEN"  
}

You will use the token from this response in the Authorization header for all subsequent requests, prefixed with "Bearer ".

Example:

Authorization: Bearer YOUR_BEARER_TOKEN

3. Configure Client IDs​

All requests require a unique clientId. This should be at least 8 characters long and relate to a unique user in your customer database (i.e. the same ID across all devices).

This is critical for us to accurately track monthly active users. If the clientId passed into the Clips API isn't a unique user ID, there's a risk of mis-counting MAUs (ex: the same user could be accidentily counted for multiple devices if a device id is passed in as a client id).