I've been doing work on standardizing the API and making the
documentation clearer so now I'm pretty close to get to the mix
creation API. The best way to get a decent API built is to bug me
about it :) If I see that devs want it, it's a good reason to do it.
I've been waiting because it's still unclear to me how it's going to
work so maybe you (and others) can propose some ideas on how it should
work. Once we agree on a good format, it should be pretty easy for me
to implement the backend.
Here's where I stand on it now. There are 3 parts to creating a mix:
1. upload tracks
2. create a mix (with name, description, tags, cover)
3. add tracks to the mix
Then, possibly, users could:
4. update the mix metadata
5. search previously uploaded tracks
6. reorder add/remove tracks from the mix
This is what the website currently does but the internal API dates
from 3 years ago it would need to be cleaned up. An alternative would
be to create a simpler API that does just 2. 3. and 4. where you would
directly upload tracks to a mix and not support reordering or
adding/remove tracks etc..
I'm not sure what's best, I'm open to feedback, what do you guys think?
Remi
Sent from my iPhone
- delete a mix
- publish / un-publish a mix
I'll get started on this soon, hopefully it won't take too long.
Remi
--
Rémi Gabillet
CTO & co-founder, 8tracks
http:8tracks.com/remi
> email to 8tracks-public-api+unsub...@googlegroups.com.