Open jpallen opened 8 years ago
Hi! Let me start by thanking you for ShareLaTeX. I've been using it for about four years and it has become my de-facto LaTeX editor.
I've got some suggestions for what you could expose via an API, although I understand that some of these might be an overkill to your business model and you might want to refrain from adding them:
The next couple of features are something that this script does not need but I think could be useful:
(If some of this is already implemented and I just didn't see it, then sorry!)
Thanks for your interest and do tell if there's anything I can help with!
Hello! I'm one of the co-founders of ShareLaTeX and this just popped up in my Google alert for new content on the web about 'sharelatex'. I've got to admire the hacker mentality here and the fact that it's well documented :)
We've recently started talking internally about creating an API for ShareLaTeX, since we've seen a few people put together ad-hoc scripts like this, and I think there's a lot of cool stuff that could be built on it. So my question for you is what would you need from a ShareLaTeX API in terms of end-points and functionality?
I guess this script would mainly need an official endpoint to download the project as a zip file? You mentioned read-write as a possibility, so what would you need there? Is there anything else that you might want to talk to ShareLaTeX about via a script, but haven't been able to because we don't have the endpoints?