Monitor Your Stream URL to Auto-Build a SoundExchange Track List

A different starting point

Most SoundExchange enrichment starts with a file: you export a play log from your automation software and add the missing ISRC and label columns after the fact. Monitoring the stream flips that around. Point SonoVault at the stream URL your listeners already tune into, and it identifies each track as it airs and logs it with its ISRC — the field a Report of Use needs and your automation export almost never carries.

It is the better starting point in two cases: when your automation log is too thin to enrich (missing albums, mangled titles), or when you want an independent record of what actually went out over the air rather than what the scheduler intended to play.

How it works

You register a stream URL with POST /v1/streams. SonoVault connects to the stream and recognises tracks continuously (via the same Beatport and AcoustID matching that powers one-shot identify), and every recognised airing lands in a log you can read back — each entry carrying the recording's ISRC.

const res = await fetch("https://api.sonovault.now/v1/streams", {
  method: "POST",
  headers: {
    "x-api-key":      API_KEY,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    url:  "https://stream.example.com/live",
    name: "My Station",
  }),
});

const { id, status } = await res.json();
console.log(`Monitoring stream ${id} (${status})`);

{
  "id": 4021,
  "url": "https://stream.example.com/live",
  "runtime_status": "running",
  "now_playing": {
    "track": {
      "id": "315587019",
      "title": "One More Time",
      "isrc": "GBDUW0000059",        // what SoundExchange wants
      /* artists, releases[].label.name, duration, … */
    },
    "started_at": "2026-07-04T14:22:07Z"
  },
  "last_recognized_at": "2026-07-04T14:22:07Z"
}

{
  "report": {
    "from":  "2026-06-01",
    "until": "2026-07-01",
    "scope": "account",
    "streams": [
      {
        "id": 4021,
        "name": "My Station",
        "summary": [
          {
            "isrc": "GBDUW0000059",
            "title": "One More Time",
            "artist": "Daft Punk",
            "play_count": 12          // one airing counts once
          }
          /* … one row per recording aired … */
        ],
        "detail": [
          {
            "isrc": "GBDUW0000059",
            "played_at": "2026-06-01T08:14:00Z",
            "duration_seconds": 320
          }
        ]
      }
    ]
  }
}

Coverage, honestly

Recognition covers what lives in the Beatport and AcoustID space, which is broad but not everything. So treat the stream log as a way to build and augmentyour play list, not as a self-certifying census. In practice that means reconciling it against the play counts your automation software already produces, and filling any gaps with a lookup on the tracks it couldn't place.

For the field-by-field requirements and the census-vs-sample rules, start with what a Report of Use requires; for the file-based route from an automation export, see adding ISRCs and labels to a RadioBoss export. SonoVault supplies the ISRC, album and label data — filing specifics and thresholds live with SoundExchange.