Connect your station to everything else: the API, webhooks and realtime events

Your station already knows what is playing, who is listening and when it went on air. Now that knowledge can leave the dashboard: a REST API for anything your account can see or do, webhooks that call your URL when something happens, and a public realtime feed for your website. All on every plan, and most of it takes an afternoon.

Three ways in, and when to use each

The rule of thumb: anything that runs in a listener’s browser uses the public feeds, because a key in a web page is a key anyone can read. Anything that runs on your own server or in an automation tool can hold a key.

Now playing and recent tracks on your website

The simplest build, and the one most stations want first. Polling the public now-playing feed every 20 seconds is covered step by step in Show what your station is playing, anywhere. Two things are new: a history feed for the last plays, and a realtime stream so the page updates the instant a track changes instead of on the next poll.

https://streaming-api.nobexpartners.com/public/stations/YOUR-SLUG/history?limit=10

{
  "station": { "id": "moonlightfm", "slug": "moonlightfm", "name": "Moonlight FM" },
  "data": [
    { "title": "Backseat Star", "artist": "The Hold Steady", "album": null, "played_at": "2026-09-08T14:03:10.980Z" },
    { "title": "Cherry Wine", "artist": "Hozier", "album": null, "played_at": "2026-09-08T13:59:02.114Z" }
  ]
}

<p>Now playing: <span id="track">…</span></p>
<script>
  var es = new EventSource(
    "https://streaming-api.nobexpartners.com/public/stations/YOUR-SLUG/events"
  );
  es.addEventListener("now_playing", function (e) {
    var np = JSON.parse(e.data).now_playing;
    document.getElementById("track").textContent =
      np ? (np.artist ? np.artist + " — " : "") + np.title : "Off air";
  });
</script>

“Now playing” in Discord or Slack

Both chat tools accept incoming webhooks, but each wants its own message format, so a small receiver sits in between: Nobex posts a track.started event to your URL, your code verifies the signature and forwards a formatted line to Discord or Slack. That receiver can be a few lines on any host that runs Node or Python — or a no-code scenario in Zapier, Make or n8n, whose webhook triggers accept the event as-is.

POST /hooks/nobex
Content-Type: application/json
X-Nobex-Event: track.started
X-Nobex-Delivery: 7c1d…
X-Nobex-Signature: t=1757340191,v1=9a4c…

{
  "id": "4f1c1a2e-…",
  "type": "track.started",
  "created_at": "2026-09-08T14:03:11.204Z",
  "api_version": "2026-09-08",
  "data": {
    "station": { "id": "moonlightfm", "slug": "moonlightfm", "name": "Moonlight FM" },
    "track": { "title": "Backseat Star", "artist": "The Hold Steady", "album": null,
               "isrc": null, "source": "autodj", "started_at": "2026-09-08T14:03:10.980Z" },
    "listeners": 42
  }
}

1. 1In Discord, open the channel → Integrations → Webhooks → New webhook and copy its URL. (Slack: create an app with an Incoming Webhook.)
2. 2Stand up a receiver that accepts the Nobex POST, checks X-Nobex-Signature — the developer docs have copy-paste Node and Python — and forwards { "content": "▶ Artist — Title" } to the Discord URL.
3. 3In Dashboard → Developers → Webhooks, add your receiver’s URL, tick track.started, and copy the signing secret it shows you once.
4. 4Press Send test event. The dashboard shows the response code right there; the first real track change does the rest.

“We’re live” on your socials, with no code

The live.started event fires when a real person takes over from AutoDJ, and station.online when the station comes on air. Point either at a Zapier, Make, n8n or IFTTT webhook trigger and the rest is their catalogue: post to a Facebook page, send a Telegram message, add a row to a sheet, email a list. The event body carries the station name and the time, which is usually all the message needs.

• Zapier — trigger *Webhooks by Zapier → Catch Hook*; use the URL it gives you as the endpoint.
• Make — *Custom webhook* module; run once to let it learn the payload shape.
• n8n — the *Webhook* node, production URL, method POST.
• IFTTT — the *Webhooks* service; note it wants values named value1..3, so a small step in between may be needed.

Sync a music folder to your library

Stations that produce shows elsewhere often have a folder that fills up — new jingles, a weekly programme, a batch from a label. With a write-scope key, a script can watch that folder and upload what is new. Uploads go straight to storage in two calls: ask for an upload URL, PUT the file to it, then confirm.

import os, mimetypes, requests

API = "https://streaming-api.nobexpartners.com"
H = {"Authorization": "Bearer " + os.environ["NOBEX_API_KEY"]}
STATION = "moonlightfm"

def upload(path):
    size = os.path.getsize(path)
    ctype = mimetypes.guess_type(path)[0] or "audio/mpeg"
    grant = requests.post(f"{API}/v1/stations/{STATION}/tracks/upload-url", headers=H,
                          json={"filename": os.path.basename(path),
                                "content_type": ctype, "size_bytes": size}).json()["data"]
    # grant = { track_id, upload_url, content_type, max_bytes, expires_in_seconds }
    with open(path, "rb") as f:
        requests.put(grant["upload_url"], data=f,
                     headers={"Content-Type": grant["content_type"]}).raise_for_status()
    done = requests.post(f"{API}/v1/stations/{STATION}/tracks/upload-complete", headers=H,
                         json={"track_id": grant["track_id"],
                               "filename": os.path.basename(path)}).json()
    print("added", done)

Pair it with GET /v1/stations/{station}/tracks?q= to skip files already in the library, and DELETE …/tracks/{id} to retire old ones. Files up to 500 MB; the same formats the dashboard accepts. Tag your files first — title, artist and ISRC come from the tags, and they are what royalty reporting reads.

A status page for your team

A single HTML page that opens the realtime stream and shows on-air state, the current track and the listener count for each of your stations — the thing a volunteer checks before messaging the group chat. Nothing to host beyond a static file, because the stream is public and the page needs no key.

• On connect every stream sends now_playing and listeners, so the page is complete immediately.
• station.online / station.offline and live.started / live.ended arrive as they happen — flip a badge, play a sound, whatever helps.
• For history and analytics on the same page, add a tiny server that holds a read key and proxies /v1/stations/{station}/stats?range=24h — never put the key in the page itself.

Start, stop and push titles from your own tools

With a write key, POST /v1/stations/{station}/start and /stop do exactly what the dashboard buttons do, with the same checks. POST …/now-playing with { "title", "artist" } sets what listeners see during a live show driven by playout software that does not send metadata itself; the next track change or the next push replaces it. POST …/play-now with a track_id plays a library track next, ahead of the rotation — handy for a “request line” form on your site that a small server relays.

The compact reference

• Keys — Authorization: Bearer nbx_live_… or X-API-Key; read or read+write scope; account-wide; revoke any time in Dashboard → Developers.
• Limits — 600 requests a minute per key, with X-RateLimit-* headers on every response.
• Errors — always { "error": { "code", "message" } }.
• Spec — `/v1/openapi.json` imports into Postman, Insomnia and any code generator.