Skip to main content

Authenticate & Make Your First Request

This guide walks you through obtaining API credentials, exchanging them for a bearer token, and structuring your first authenticated request to the Feed Clips API.

Prerequisites​

  • An account on Clips Studio. This is the web app where you can find your API credentials, browse the catalog, and view engagement analytics.

Step 1: Get your API credentials​

Sign into Clips Studio and navigate to the API page. You will find your token and secret there. Keep these values secure. They are used only during authentication, not on individual API calls.

Step 2: Authenticate to get a bearer token​

Send a POST /v2/authenticate request with your token and secret. The API will return a short-lived bearer token. See the Authenticate endpoint reference for the full request and response contract.

The bearer token is short-lived. Your integration should authenticate at the start of each session (or when a request fails with a 401), and cache the returned token for the duration of its validity.

v1 vs v2

In v1, the authentication endpoint was POST /authenticate. In v2, it is POST /v2/authenticate. The credential format (token + secret) is the same; only the path changed. See the v1 Authenticate reference if you are working with a legacy integration.

Step 3: Send the bearer token with every request​

Once you have a bearer token, include it in the Authorization header of every subsequent request:

Authorization: Bearer YOUR_BEARER_TOKEN

All requests must be made over HTTPS to https://api.clips.feed.fm.

Step 4: Include clientId on every request​

Every API request also requires a clientId parameter that identifies the end user. This must be a stable, unique identifier for each user in your system. It should be the same value across all devices and sessions for that user.

See Client ID for the full requirements and guidance on choosing an appropriate identifier.

Business Model Credentials​

During onboarding, Feed will provision separate API credentials for each business model you offer (for example, Ad Supported and Subscription). This allows song play data to be reported to rights holders separately for each model. You will see distinct sets of production and development credentials in Clips Studio for each business model.

Work with the Feed.fm team to confirm the correct credentials are in use before launch. See the Go-Live Checklist for the full pre-launch verification steps.

Next steps​