In lieu of an api, can we have a faster automated export? I can hack this by scripting into chrome, but it’d be great to just be able to call paperpile.com/JSON and get my JSON formatted library at will. Limiting to ~20 calls a day or whatever works would be reasonable to stop abuse, and I’d imagine for a good portion of what people want the API for this would suffice (e.g. Bibtex slickening, trend tracking, etc).
Thanks.
Thanks for the feedback, @steingart. We are about to release betas for dedicated BibTeX export options and Overleaf integration. The intention is for this to pave the way towards more workflows for exports and other features according to user demand, so I’ve logged your feedback under the topic in our tracker for the team’s consideration.
I use bibtex export, which is great, but cumbersome.
Ideally I would have a script that would download bibtex for a folder and update a local file.
The current system downloads with a changing filename to my downloads folder, and I can’t change that.
It would be easier to have a stable filename. I could then copy the updated file into place and accept to overwrite. Currently, I have to have two folders open to move the file, delete the old file, rename the new one. This becomes really frustrating.
There are a few posts about APIs where the answer includes “depends on user demand”. How do you actually assess that demand?
Thanks for sharing your workflow, @Hamish_Harvey.
You don’t need to manually download and rename your BibTeX files each time. Paperpile has an automatic BibTeX export feature that can create a .bib file with a stable filename, which stays in sync with your library or with a specific folder/label.
This help page shows you how to automatically sync a folder to a BibTeX file in Google Drive, GitHub, or a downloadable web link.
Thank you! 
And sorry not to have looked very hard for that.
