​
Overview

The Backlog Audio dataset provides access to audio files from past events. Each event includes two URLs to allow for both streaming and downloading.

​
How it works

The audio data can be accessed through a unique URL and is served in both MPEG format for downloading and M3U8 format for streaming, which can be used in compatible media players to play or download the file. This data includes event-specific information, such as company and event identifiers, ensuring easy retrieval of relevant metadata.

​
Chapters

The Chapters endpoint provides structured segments associated with an audio file. Chapters allow clients to divide long-form content into meaningful sections, making navigation, playback, and indexing more intuitive. Querying with an audio id returns a paginated list of chapter objects. Each chapter includes metadata such as title, timestamps and hierarchy level.
Only level 1 chapters are returned by default. To retrieve level 2 and higher chapters, you must explicitly query those levels using the levels query parameter.

​
Levels and Nesting

The level field defines the hierarchical depth of a chapter within the audio file.
  • Level 1: Top-level sections (e.g., “Prepared Remarks”, “Q&A”).
  • Level 2: Subsections nested within a level 1 chapter (e.g., individual topics within “Prepared Remarks”).
  • Level 3+: Further nesting is possible for finer granularity (e.g., subsections within a subsection).
Chapters are always contained within the timestamp range of their parent chapter. For example, all level 2 chapters will fall within the start and end timestamps of their level 1 parent.
Clients must be prepared to handle arbitrary depth of chapters (level 1, level 2, level 3, and beyond). If your application only supports specific levels, you should explicitly query those levels.
See API reference for more details.

​
How to access the data

The API allows you to query the Backlog Audio dataset using a variety of parameters, such as ticker, ISIN, date, and more. You can also use the API to retrieve a list of all audio available in the dataset. For more information on how to use the API, see the API reference.
The audio data is available for download and streaming. The download URL is a direct link to the audio file, while the stream URL is an M3U8 playlist that can be used with compatible media players.
The data is served through a global CDN, ensuring low latency and high availability. The URL is unique to each audio file and customer. It should not be shared with others nor altered in any way as it may result in a loss of access.

API Reference

Explore the Backlog Audio API endpoints.

​
Example

Below is an example of how to consume an audio stream. Make sure to use the streamUrl from the API response to replace the placeholder in the code. An example is also available at CodePen.
html
<!doctype html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>Play M3U8 Audio</title>
  </head>
  <body>
    <h1>Audio Stream</h1>
    <audio id="audioPlayer" controls></audio>

    <!-- Include Hls.js library -->
    <script src="https://cdn.jsdelivr.net/npm/hls.js@latest"></script>
    <script>
      document.addEventListener("DOMContentLoaded", () => {
        const audioUrl = "your-audio-stream.m3u8"; // <<< Replace
        const audio = document.getElementById("audioPlayer");

        if (Hls.isSupported()) {
          const hls = new Hls();
          hls.loadSource(audioUrl);
          hls.attachMedia(audio);
          hls.on(Hls.Events.MANIFEST_PARSED, function () {
            console.log("M3U8 manifest loaded, audio is ready to play");
          });
        } else if (audio.canPlayType("application/vnd.apple.mpegurl")) {
          audio.src = audioUrl;
          audio.addEventListener("loadedmetadata", () => {
            console.log("M3U8 audio is ready to play");
          });
        } else {
          console.error("HLS is not supported in this browser.");
        }
      });
    </script>
  </body>
</html>