Getting started with Tuned Global

1

Start with the API Playground

Go to: API Playground

Access: Log in to your CMS account to retrieve your StoreId, AccessKey, and SecretKey, then use these credentials in the API Playground. No prior user registration is required to get started.

The API Playground gives you the quickest way to familiarise yourself with Tuned Global's APIs without having to build anything first.

Start here to understand the basic API journey and see how requests and responses work.

Follow the guided flow to:

1. use your environment credentials and follow the authentication flow;
2. create or authenticate a test user where required and obtain the token used for user-level API calls;
3. make your first API requests;
4. search and retrieve content from the catalogue; and
5. test the APIs involved in delivering a basic music experience.

The Playground allows you to understand the sequence of API calls before reproducing them in your own application.

Need more detail? See Authentication and API reference.

2

See the APIs working in the Web Player

Once you have familiarised yourself with the APIs, open the Web Player.

Go to: Web Player

Access: If this is your first visit, enter the StoreId you used in step 1 and create a user account directly in the Web Player. This is an end-user account and is separate from your API credentials and CMS account. You can use the same user account across the Web Player, PWA and supported mobile applications for your environment.

The Web Player gives you a working example of how Tuned Global's technology can be used within a real streaming experience.

As you navigate the player, you can see how the application interacts with Tuned Global's APIs and connect what you tested in the Playground with an actual user experience.

Try searching for music, browsing content and playing a track while looking at the API interactions behind the experience.

This helps bridge the gap between individual API calls and the way those APIs work together within an application.

Note: you can see the same front-end experience in the WPA or mobile app too, but you won’t see the API call panel.

3

Explore content management in the CMS

This step is optional but highly recommended to understand the full journey. It is only applicable if you have CMS access.

Go to: Autotune CMS

Access: CMS accounts are invitation-based. If CMS access is included for your project, you will receive an email invitation from Tuned Global. Activate your account from that email before signing in. Your CMS account is separate from your Web Player user account.

The CMS allows you to manage elements of the experience without building them directly into your application.

A simple way to understand how the CMS, APIs and Web Player connect is to create a playlist.

Create a test playlist in the CMS, then open the Web Player (or the WPA app or the mobile app) to see how that content becomes available within the experience. The same playlist can also be retrieved through the relevant APIs.

This gives you a practical example of how content created or managed in the CMS is consumed by applications using Tuned Global's Music Cloud Platform.

If you are focused purely on API integration and do not need to explore content management yet, you can skip this step and start building.

Need more detail? Watch more CMS training videos and see how to use system playlists.

4

Build your own environment

Once you understand how the APIs behave in the Playground and have seen them working within the Web Player, the next step is to reproduce the journey in your own application.

Go to: Music streaming quick start

Follow our Build a music streaming service quick start to create a simple implementation using your own development environment.

The guide takes you through the core steps needed to move from authentication to accessing catalogue content and streaming.

Because you have already tested these interactions in the Playground, you should now recognise the API sequence and understand what each part of the integration is doing.