Hi everyone! Dave here from the engineering team. I just got a direct message from a user asking about a topic we talked about last year and after I wrote the response, I figured it'd be a good thing to post up to our group page as well.
The question was (paraphrased): When is the Public API you've talked about going to be available?
And here's my answer back! Longer read, so get a drink...
Yes, we were hoping to have a public API available this year but we don't have it available just yet. The main reason for this is the large scale changes that are currently in progress. While we'd originally hoped to be able to re-work the structure of the current app quite a bit, our efforts earlier this year led to the discovery that we need to do some much deeper foundational work. Basically, the app right now is a single entity, and with that comes some issues. First of which, there's no reasonable way to provide a public API that would be performant by any stretch. Too many wires are currently crossed to open those gates.
So we're currently, and have been for several months now, undergoing numerous large scale efforts to re-do the entire foundation of the app and shift to multiple service-driven components. This will bring us huge gains in reliability and scalability, but comes with the cost of pushing back a public API until that new architecture is fully implemented.
We'd love to have this API available sooner, but it's more important we finalize a solid architecture first and avoid the pitfalls that happened a couple years ago with the launch of the current site. Once those details are smoothed out, and since it'll be entirely service oriented, opening up a public API will not only be possible, but be doable in a way that provides solid security and an overall great user experience, both for those on the site and various apps, as well as anyone who decides to utilize the API directly!
We've gone through a lot of changes in the past year, and all though our size of projects has increased vast amounts, our team has not, so I'm hesitant to give you any time estimates at this point so as to not establish false expectations. I'd say once the new SVOD experience is done and we wrap up most of the implementation of the new Community experience, we'll be in a good spot to start pushing for a public API. We'll be announcing those things over the next few months and you'll be hearing much more about the new SVOD experience very soon.
I'm excited to know that there are so many of our community members that actually want API access and its a personal goal of mine to ensure our engineering team delivers that! It may not be right around the corner, but I assure you it will be great when it does arrive!
After I sent that response a question popped into my head, which is the main reason I'm posting here. What kinds of things would you all want out of a Public API? What would you be building with it? Nothing is finalized in any fashion as far as what that will look like, so now is your chance to get in your wish-list items and maybe share some ideas about what kinds of things would be fun to build with an RT API.
Engineering <3's you all!