Catalog for Experiences

This page is for Experiences clients. You hold the media rights to the content (a league, team, federation, or similar). Catalog docs call that role a rights holder. You use Experiences and the Experiences SDK in your own apps.

Catalog is a pull API that returns a content feed as JSON. You request a Stories, Moments, or Videos feed, take content IDs from the response, and pass those IDs into the Experiences SDK so your app shows that content. Labels are the simpler alternative when you don't need ID-level ranking.

If you use Catalog HTML links and you don't use Experiences, start at Catalog for publishers instead. For the audience split, see Content catalog.

What Catalog returns

Endpoints are segmented by content type: Stories, Moments, and Videos. You retrieve content by page or by content ID. The JSON structure is similar per content type, with differences on the response pages.

The feed returns content you hold rights to and have agreed to share through Catalog. You won't see everything WSC Sports holds.

Catalog is the pull half of this integration. To be notified when content changes instead of polling, see Updates. For content ranked by WSC Sports rather than queried by you, see Recommendations.

Use Catalog with the Experiences SDK

You choose what the Experiences SDK serves using labels, content IDs, or a mixture of both.

• Labels: map viewer preferences to content labels in Arena.
• Content IDs: call Catalog, query the feed using viewer preferences, rank the returned content IDs, and pass the ordered list to the SDK.
• Mixture: combine labels and content IDs when your product design allows it.

For setup, see Explicit personalization.

Label-based selection needs less processing than ranking Catalog IDs yourself.

Call format, authentication, and endpoints are on Content catalog API.