Skip to content

Introduction

The Soundtrack SDK provides a comprehensive set of tools and C APIs to build a custom music application that connects directly to the Soundtrack service. It enables developers to create fully integrated music players, manage playback controls, access track metadata and interface with platform-specific audio backends.

Who It Is For

The SDK is available to selected Soundtrack partners building commercial music playback systems — including embedded hardware, smart devices, and custom applications — with a potential deployment scale of 5,000+ locations.

Before you start, read the requirement page to make sure your hardware is compatible before you reach out.

Become a Partner

The process of accessing the Soundtrack SDK and becoming a Partner:

  • Submit a Partnership Request Contact our team at sdk@soundtrack.io to express interest in integrating with Soundtrack.
  • Sign a Non-Disclosure Agreement (NDA) The NDA is sent by us which ensures that all SDK documentation, binaries and processes are protected.
  • Provide Your Toolchain We use this to build a shared library tailored to your target platform(s) which we will send to you once built.
  • Integrate the SDK Read through the documentation and example code to implement your player, including authentication, audio output, and controls. We'll provide ongoing support, usually in a Slack channel as needed.
  • Certification & Review Once your implementation is complete, we'll run a certification process to ensure compliance and quality.
  • Launch & Support After passing certification, you're ready to go live!

Responsibilities

The Soundtrack SDK is a collaborative effort between Soundtrack and its partners. Each party has specific responsibilities.

Soundtrack Responsibilities

  • Providing our SDK; library and header files (e.g. libsplayer-x.so and splayerapi-x.h) built using your toolchain.
  • Backend infrastructure used by the SDK.
  • Support during development.

Partner Responsibilities

  • Application lifecycle.
  • Application monitoring.
  • Audio processing of the SDK output.
  • All source code except for splayerapi-x.h.
  • Library update mechanisms
  • Updating the toolchain to make sure it supports a C++ standard that is at most 5 years old at any given time now and in the future.
  • Adhering to the Soundtrack brand guidelines provided by us.

SDK terms and use

All applications using the Soundtrack SDK must comply with the Soundtrack Terms & Conditions, and must be certified before commercial release. Significant changes made after launch require re-certification before they can be deployed. The Soundtrack terms and conditions can be found here. For more information regarding the certification process, please refer to the certification guide.