Soundtrack SDK | Docs

Table of Contents


The Soundtrack SDK enables you to build support for Soundtrack on your platform. By combining expert curation and world-class tech, Soundtrack Your Brand provides a beautiful all-in-one solution for streaming music to stores, hotels, restaurants, and other commercial settings.

The SDK is available for selected partners. If you’re interested in becoming one, please reach out to (applications currently open for opportunities of more than 5000 locations).

This page contains the documentation for the SDK. In order to use it, you will need our latest build (which we need to send to you).

Soundtrack SDK is the package containing all code and documentation needed for you to get started. Splayer API is the local API within the SDK, used for initiating and controlling playback.

Unless anything else is communicated by Soundtrack, the application shall be named “Soundtrack Player”.






Detailed changelog can be found in the SDK package.

Date Version Changes Included APIs
Q4, 2017 1 First draft including basic functionality. splayerapi v1
Q2, 2018 2 Moved controls to a separate API. Clarified examples. splayerapi v2, splayerapi_control v1
Q4, 2018 3 Major/minor versioning. New metadata API. Some config variables renamed for clarity. splayerapi v3, splayer_controls_api v2, splayer_troubles_api v1, splayer_audio_api v1, splayer_metadata_api v1

Getting started


Make sure that you have:

All applications must be in line with the terms & conditions and be certified by Soundtrack (see certification criteria further down on this page).

What’s in the package?

Note: The package can’t be find on this page. It will be sent to you by Soundtrack. A static library version can be provided. It is not included by default due to the increase in size of the package

Soundtrack - Overview

We highly recommend that you play around with your Soundtrack account so you get an overview of the product prior to using the API. All guides and frequently asked questions regarding Soundtrack can be found on our help pages.

It’s extra important that you understand the hierarchy, where one account (e.g. “Ludwig’s Burgers”) can have multiple locations (e.g. “Flagship restaurant, Stockholm”) which in turn can have multiple sound zones (e.g. “Bar”, “Restaurant area”, “Staff room”).

Each sound zone can only have one device. Soundtrack supports multiple device types (see our help pages to see which ones). The rationale for having multiple sound zones is that you want different music in different parts of the same location. If you want the same music everywhere in the same location you’ll only need one device and then distribute the music with your audio system.

Create a device

Before we can run an application using the SDK we must create a device using the Partner API. This device will be unique and needs to be paired to a sound zone. A device can only be paired with one sound zone at a time. The Partner API is a GraphQL API and you can run the following to create a device. Note: you need your Partner API credentials to do this step. It only needs to be done once since the pairing code does not change.

  1. Go to (this is just an explore tool, you should of course implement this code where you find it suitable)
  2. Add the Authorization header. In the “Value” field, write “Basic ” where are the Partner API credentials that you should have received from Soundtrack. Ensure that you copy the full base64-token including the == on the end


Authorization: base64encode(client_id:client_secret)
  1. Enter a GraphQL query in the top box
    mutation PartnerCodeCreator($input:GeneratePairingCodesInput!){
     generatePairingCodes(input: $input) {
         codes {
  2. Include the query variables
     "input": {
         "deviceType": "EMBEDDED",
         "label": "Partnername M324",
         "hardwareIds": ["partner_id_ab12"]
    • Change the description to add information about the platform (will not be shown to users)
    • Set deviceType to EMBEDDED (currently not optional)
    • Change the label to the product’s name (will be shown to users)
    • Change the hardwareIds entry to the hardware_id of your choice. See “Authentication & Pairing” for more info
  3. Run the query and you should get a pairing code as output. You will need this code to pair the created device with a specific sound zone later.
  4. Write down the hardware_id that you chose (in the example ‘partner_id_ab12’). Write down the pairing code that was output when you ran the query

Pairing a device with a sound zone

  1. Go to Soundtrack (
  2. Press “Locations”
  3. If you have no location set up. Create location using the “Add Location” button
  4. When the location is created, you need to create a sound zone
  5. Press the options button to the right of the location
  6. Add a zone with a name
  7. Click on the new zone
  8. Pair your player application by choosing “Hardware Device”
  9. In the input field, enter the Pairing Code that you got when creating a device.
  10. The device should now be paired with this sound zone.

Building and running the example code

  1. Unpack tar ball (sent to you by Soundtrack)
  2. In the /src folder there are several examples showcasing some basic setup of a player application
  3. Open any example file, and change the parameter: hardware_id to the hardware id you created in the “Create a device” section (“partner_id_ab12” in above example)
  4. We also need to provide the vendor secret to the application (will be sent to you by Soundtrack). This can be done in a few different ways:
    • Set the value directly in vendor_secret
    • Set -DVENDOR_SECRET=xxxx when building with cmake
    • Add the vendor secret directly in the CMakeList.txt file
  5. Build the project using cmake
  6. There will now be several example targets in the build root folder
  7. Run the example executable (eg. libsplayer_simple)
  8. There should be some console output and music should start playing shortly
is_playing() = false

alsa_open samp: 44100 channels: 2
Alsa initialized, buffer_size: 88200 period_size: 22050
Couldn't find PCM 'PCM' volume control.
alsa_audio_impl::audio_pause: 0
  9 21:56:36 tyson                    warn             job.cpp:161  Slow timer, seconds: 0.052278248003858607, context: "from: dsp.cpp:344 schedule_setup"
 alsa_audio_impl::audio_pause: 0
ERROR: EBADFD: Let's prepare alsa again
snd_pcm_prepare returned 0

Reference implementation

In the package distributed by SYB, you will find an array of example implementations. Feel free to modify as you wish.

Authentication & Pairing

Splayer API is only aware of Vendor Hardware ID, which is something that you as a vendor chose, and a Vendor Secret that you will get from Soundtrack. The hardware ID is used to generate the Device ID in the Partner API (see Create a Device above). The reason Soundtrack Device ID’s are used for pairing is because they are guaranteed to be unique, even though two vendors might have the same Vendor Hardware ID for two different devices. This way we avoid name clashes for devices.

Second reason, is that our website is open for all customers, which means a user can have devices from multiple vendors and the end user would then need to pick from a list of vendor. It wouldn’t be the best user experience, it would be easy to make mistakes and the user himself could guess a Vendor Hardware ID and do a denial of service for somebody else.

Upgrade and provisioning

Splayer API is provisioned by Soundtrack’s backoffice systems with rollout limited to a certain percent of all devices, or at a certain time of day considering local time zone of the device. Below are two different endpoints to use to retrieve the latest version of Splayer API for two different platforms (Ubuntu 16.04 64-bit, Ubuntu 16.04 32 bit).

"id": "QnVpbGQsLDFsZ2g1bW1uNnJrLw..",
"version": "48.17-308",
"link": "",
"checksum": "9e12bb0ded21711ea1c666dc776b2751febcc01f",
"platform": "splayer-x86_64"

The two important fields are version and link, you can disregard all other fields in the JSON. In the example above the version is hashnumber, since the example is not from a proper release, but the latest build. The link points directly to the library.

The checksum is a sha1 hash of he file in the link, make sure to verify the checksum matches for security and reliability reason!

To get provisioning working you need to send three HTTP headers. Basically each device sends a Vendor Hardware ID as described above and a Device Vendor ID. In the example below the Vendor Hardware ID is 28cfe91fcc6d.


Example of adding HTTP headers with cURL

char buf[1024];
snprintf(buf, sizeof(buf), "X-Device-Id-0:%s", device_id);

struct curl_slist *chunk = NULL;
chunk = curl_slist_append(chunk, "Accept:");
chunk = curl_slist_append(chunk, "X-Device-Key-0:eth0");
chunk = curl_slist_append(chunk, buf);
curl_easy_setopt(curl, CURLOPT_HTTPHEADER, chunk);

Approval process and certification

The application built is to be approved by Soundtrack and shall at all times adhere to the certification criterias (see: Certification).

Release management

Please note that the below release information relates to the player software within the SDK, so it’s not the SDK and the splayer-APIs per se.

Release SDK player software

The player software is updated monthly according to a set schedule. Unless anything else is communicated the release will be done on a Wednesday between 02.00 and 06.00 (based on each player’s local time).

Patching SDK player software

Every Thursday Soundtrack decides if there is a need for a patch the coming week. The reason for a patch is either an incident or an important bug.

All times below are CET/CEST. Consider that the times below are deadlines.

If you did not get in touch with us, you will have to wait until next full release to get the patch.

Release schedule

Date Release
10 Apr 2019 Pre-release 48
17 Apr 2019 Full-release 48
15 May 2019 Pre-release 49
22 May 2019 Full-release 49
19 Jun 2019 Pre-release 50
26 Jun 2019 Full-release 50
3 Jul 2019 Pre-release 51
10 Jul 2019 Full-release 51
31 Jul 2019 Pre-release 52
7 Aug 2019 Full-release 52

* Dates marked as red are changed release dates according from the original plan.


Older version of libstdc++ and running on the target.

Depending on GCC version you might have an older version of libc, libstdc++ and ld. We are running GCC 6.4 and 7.0 in production.

./libSplayer_alsa: /lib/ version `GLIBCXX_3.4.20' not found (required by
./libSplayer_alsa: /lib/ version `CXXABI_1.3.8' not found (required by
./libSplayer_alsa: /lib/ version `GLIBCXX_3.4.19' not found (required by
./libSplayer_alsa: /lib/ version `GLIBCXX_3.4.21' not found (required by

If needed we can link libstdc++ statically to avoid most of the issues, but your target platform needs a compatible (glibc). Use the same version of libc and libstdc++ on your target as in the toolchain that you provide us. For Linux, you can create them using Yocto or Buildroot. Be aware that we are using atomics from c++ 11, and some gcc toolchains put these in a separate library called This library is required on the device for our player to run.

Audio stutters

On some hardware we have seen ALSA defaulting to a very small buffer size. A 44.1Khz two channel PCM stream is 88 200 samples/per second. In the below example that’s a context switch 200 times a second (every 5ms). Now a small buffer size is great for low latency, game and sound applications where instant sound feedback is needed on user input. This is not the case for audio streaming. With these small buffers we can’t feed ALSA with audio fast enough, so we will get -EPIPE from snd_pcm_writei().

Alsa initialized, buffer_size: 1323 period_size: 441

Set the ALSA buffer size to at least 1 period (second). For 44.1Khz two channel PCM stream is buffer size 88 200 samples and a period size of 22 050 samples. We have provided the code in callbacks_alsa.c. You could try to set the buffer size to 4 periods instead.

Alsa initialized, buffer_size: 88200 period_size: 22050




Certification process

Type Test case Instructions Expected behaviour
Setup 1.1 Start the device. - The device should be intuitive to install and come with necessary instructions. - It should be simple to start the Application.
. 1.2 Ensure Application has connectivity Clearly stated whether or not the Application can access Soundtrack
. 1.3 Find the device ID - The device ID shall be easy to find. - If the device ID is generated in the Application, this generation should take less than one second. - The device ID shall not be generated more than once (not needed, since the request always will give the same response). - When creating the device ID, the correct label and description should be set. - Clearly stated what the device ID is used for and how to use it in order to connect the Application to Soundtrack. - The label-field used when creating the device shall be correct.
. 1.4 Pair the Application in Soundtrack and assign a soundtrack Music should start playing within 2 minutes.
. 1.5 Ensure config variable bandwidth_limitation_kbps is set to at least 2000 kbps. Music playing.
Actions in web interface ( 2.1 Skip track Track skipped
. 2.2 Press pause Track paused
. 2.3 Press play Track resumed
. 2.4 Increase volume to max Volume set to max
. 2.5 Decrease volume to zero Volume set to minimum
. 2.6 Change soundtrack New soundtrack should start playing after the current track is done
Playback (offline) 3.1 Cut off internet access (e.g. by plugging out the ethernet cable) when the device is powered on Music should keep playing
. 3.2 Start device without internet access Music should keep playing
. 3.3 Enable internet again - Music should keep playing. - Device should go online in Soundtrack.
Playback - poor internet connectivity (ensure that you have music cached offline for this step) 4.1 Set up network according to profile “100% Loss”. See below. Music should keep playing
. 4.2 Set up network according to profile “High latency DNS”. See below. Music should keep playing
. 4.3 Set up network according to profile “Very bad network”. See below. Music should keep playing
. 4.4 Set up network according to profile “Edge”. See below. Music should keep playing
Updater 5.1 None - Contacts Soundtrack’s update service every 15 minutes (if the device is online). - If new SDK available: download. -When new SDK downloaded: quit Application at end of next song. - If installation fails: fall back to previous SDK version
Watchdog 6.1 Make sure the application is running, then ask Soundtrack to simulate a crash remotely - Application should be restarted. - Music should start playing within 30 seconds.
Test latency on actions (implementation of these actions are not mandatory) 7.1 Skip track (e.g. using a button on the device or in the application) Track changed within 1 second
. 7.2 Press pause (e.g. using a button on the device or in the application) Track paused within 1 second
. 7.3 Press play (e.g. using a button on the device or in the application) Track resumed within 1 second
. 7.4 Change volume (e.g. using a button on the device or in the application) Volume changed within 1 second
. 7.5 Show result from troubleshooting endpoint (e.g. exposing if device is paired or not in the application) Correct information exposed (e.g. if the device is not paired to Soundtrack)
Stress test (final boss) 8.1 Assign the soundtrack ‘SDK Certification’ and play for one week Music playing
General 9.1 Check for Soundtrack marketing material (e.g. logos) Material not in breach with marketing guidelines

Poor internet connectivity profiles

. 100% loss High latency DNS Very bad network Edge
Downlink bandwidth No limit No limit 1 Mbps 240 Kbps
Downlink packets dropped 100 % 0 % 10 % 0 %
Downlink delay 0 ms 0 ms 500 ms 400 ms
Uplink bandwidth No limit No limit 1 Mbps 200 Kbps
Uplink packets dropped 100 % 0 % 10 % 0 %
Uplink delay 0 ms 0 ms 500 ms 440 ms
DNS delay 0 ms 3000 ms 0 ms 0 ms