Ok, I'm actually just a listener
A few days ago, tho, my favourite station switched from radiotuna to spacial and now my "nowplaying" script for twitter stopped working, i.e. I just can't figure out how to poll track info.
Your api looks kinda promising, yet the only command I found so far is
/api/rest/station-info-service/get-sv-player-info
Is there a manual for this?
What I'd need to know is if something like "get-track-info" exists and its correct use
Any help is appreciated
Thanks

Spacial actually offers three types of streaming services.
SAM Vibe => Automation in the Cloud
Cheapeststream => Traditional Stream hosting with limited options and cheap prices
SpacialNet => Traditional Stream hosting with more options and higher prices

The first one has an API, but that's undocumented and thought for internal use only.
For reverse engineering that, you might want to have a look at the Web widget of SAM Vibe.

The other two have no API at all. They are just basic Shoutcast (v1/v2) or Windows Media Servers and expose the default statistics interfaces over HTTP as these servers always do.

_________________
Benedikt Bauer - SVS (Spacial Volunteer Support)

We're offering custom PAL / PHP code and general SAM assistance at palscripts.com

My Project:
Send "Now Playing" from SAM to Twitter and/or Facebook | Sourcecode

I did that.
But the only thing I was able to catch via fiddler was the initial station info.
All the other data seems to be polled "internally" with just a javascript event subscription to update specific html elements.
I also let wireshark loose on it and found that the info is also sent within the "lame" mp3 header frames.
It's just that it'd be total overkill to scavenge these bits of data that way.
So a nice clean request & json response would be very helpful

Wow, looks like you dug deeper than I ever did.
The problem is that this is not a public API. It's a REST webservice, but only for internal use (the web widgets in particular).
Therefore no public documentation exists. (I have no idea if there is ANY documentation at all or if this knowledge is just shared "under the hand" between devs working on that part)

You COULD try and ask spacial support about the API. However chances are rather slim that they will reveal anything.

_________________
Benedikt Bauer - SVS (Spacial Volunteer Support)

We're offering custom PAL / PHP code and general SAM assistance at palscripts.com

My Project:
Send "Now Playing" from SAM to Twitter and/or Facebook | Sourcecode

Oh well, thanks anyway

I might be able to draw info from their tunein, too. But I noticed they don't update it that regularly. Often enough it just displays the name of the show/DJ itself.

No real bigge. No one's life gonna change if I drop the station from my polling list for now
I will keep an eye on it if something crops up, tho

Never had this kind of problem with other stations, no matter which system they were using. Maybe I was just lucky. For example, BBC can be polled directly (http://polling.bbc.co.uk/radio/realtime ... _two.jsonp), radiotuna offers a "backpassage", as does streamlicensing.

I didn't have time to look into the Web widgets myself yesterday, but now I did.
In fact it's pretty easy to get all the info you like.

The API looks like this:

Queue/Coming up:

Example: https://samweb.spacialaudio.com/webapi/ ... allback=cb

History/Recently played:

Example: https://samweb.spacialaudio.com/webapi/ ... allback=cb

Response Format is JSONP (a human can easily decode JSON from that, it's basically a JavaScript function call with an object containing the result as the sole parameter)


You can get the SID from the listen link for normal players. The token is the last part of the id of the div where the widget is rendered in.
This for example would be the widget for one of my SAM Vibe stations:

The widget script extracts the token as whatever is written after the third - in the id attribute.

If you don't want to code yourself, the API script is pretty well readable (at least if you skip the first couple hundred lines that just contain a minified version of jQuery and only read the code written by Spacial)
http://media.spacial.com/widgets/samcloud-webapi.js

And this would be the widget script that calls the API functions and renders the Widget in HTML:
http://media.spacial.com/widgets/widget ... pe=defined

The API has different base URLs depending on the environment, but I think all the SAM Vibe instances "out in the wild" run on the production environment.

_________________
Benedikt Bauer - SVS (Spacial Volunteer Support)

We're offering custom PAL / PHP code and general SAM assistance at palscripts.com

My Project:
Send "Now Playing" from SAM to Twitter and/or Facebook | Sourcecode

Wow.
Thank you so much!

This part of the app is now up and tweeting again

These request not showing up in any sniffing tools puzzled me to no end. Having breakpoints in the respective functions (those that are handling the updates to the controls) didn't help much either. The script seems to get reloaded over and over, so the breakpoints become void.
Thanks again

Sometimes it helps just reading the code

I'd be interested in seeing what you built from the API, though.

_________________
Benedikt Bauer - SVS (Spacial Volunteer Support)

We're offering custom PAL / PHP code and general SAM assistance at palscripts.com

My Project:
Send "Now Playing" from SAM to Twitter and/or Facebook | Sourcecode

Just a tiny .net/C# app, polling info from various stations, checking it against a "white list" of my favourite artists and songs, and firing off tweets whenever there's a match