As a segment transcoding API user, I cannot use some of the values returned to me about studio HOT 1 OPEN

Hmm, going through these:

streamKey
playbackId

These two aren't useful to a segment transcoder, true, but they are useful to programmatically create RTMP streaming endpoints through the API. Usually that's done through the UI, but it still seems like a valid use case.

userId

Perhaps not useful to an end user at this time. But it is pretty useful to admins, who can list lots of streams and look up the user for each. Also potentially useful to systems that have custody of streams from lots of different users — imagine Mist looking at all of its stream objects to see how many unique users are utilizing the server right now.

renditions

I think LivepeerWowza might still use this, I'd have to check. Definitely legacy and should probably be removed and fixed in LivepeerWowza.

kind

Yeah, I mean, objectively useless right now. But I usually include this field in APIs I write... it becomes useful if we ever have a "watch for changes" kind of feature, whereby a user would keep a socket open and be sent new API objects over the wire when changes occur.

What's the goal, here? I imagine we're trying to make things easier for folks going through this process on the command line? Two changes we could make that could help in that case: 1. we could return formatted JSON objects, so you can see all the fields with indentation and whatnot and 2. we could reorder the fields such that the things we care about most are at the top.

from studio.