Will you be supporting the Streaming API? about 7digital-api HOT 3 CLOSED

Not at the moment; it will but I can't make any predictions about when. Supporting the entire API is a blocker for getting to v1.0. There is still some not-insignificant plumbing work that would need to happen for us to provide a way of accessing streaming endpoints consistent with other parts of the API because the streaming services are on a different host.

That said, accessing track/preview is currently possible because I exposed the lower level oauth signing and it might be possible to extend it further to provide an interim solution that would prevent you needing to use another (or, perish the thought, implement) an oauth signer. How soon are you likely to need it?

from 7digital-api.

Thank you for your response!

@raoulmillais a timeline of two weeks to have an interim solution would be perfect. We are on the verge of signing a contract with 7Digital and upon signing this we'll be needing a solution as soon as possible after that. One of our products will be a page with a music player that has DMCA compliant playlists. I can work with the preview endpoints until then, and hopefully by the time the mock-up is done there your package will be able to support those endpoints.

from 7digital-api.

I actually think the interim I proposed is the best solution since it leaves it up to consumers to decide how to request the actual media bytes. I've published this in 0.26.0 and so you can now use Oauth.sign() to sign streaming requests on behalf of users without 3rd party user management if you update. I've updated the docs to reflect the changes, feel free to submit another issue if it's unclear.

from 7digital-api.