CMS

The Tuned Global CMS, Autotune, is where teams create, organise, and manage the content that powers their digital music and media experiences.

It is used to manage editorial and operational content such as playlists, stations, carousel items, promotional pages, tags, discovery structures, and other CMS-driven experiences.

For API-led services, the CMS acts as the editorial layer behind your application. Your team manages content in the CMS, while your front end retrieves and displays that content through Tuned Global APIs.

This means that some of the values developers need, such as a content key, playlist ID, station ID, carousel item, or tag value, originate in the CMS rather than in code.

What you can do in the CMS

Use the CMS to:

• Create and manage playlists, stations, and radio experiences
• Configure homepage content, featured carousels, shelves, and promotional pages
• Organise catalogue content using tags
• Manage artwork and content metadata
• Publish content so it can be surfaced in your app
• Refresh or clear cache when content updates need to appear quickly

Who this section is for

This section is useful for:

• Content and editorial teams managing app experiences in the CMS
• Product teams planning how content should appear in the app
• Developers integrating CMS-managed content through Tuned Global APIs
• Implementation teams who need to understand how CMS objects map to API responses

If you are building an app or integration, start with CMS and API integration to understand how CMS-managed content is consumed through the APIs.