Does Paper still support export as Markdown?

[companion]

I'm trying to use the Dropbox API to access Paper documents as markdown. I have a connected app and a user with the new version of Paper (paper_as_files: enabled). I've switched from docs/download to /files/export as per the migration guide, but it doesn't appear that endpoint offers any method to select the export format.

So, is Markdown export still a thing, and if so, how do I do it?

[Greg-DB · Accepted solution]

No, unfortunately /2/files/export doesn't support exporting as Markdown, nor is there another way do that in a 'paper_as_files' account, but I'll pass this along as a feature request. I can't promise if or when that might be implemented though. 

---

Update: the /2/files/export endpoint now supports exporting .paper files as Markdown.

[companion]

Okay, thanks. That would have been really useful - I've looked at the HTML export, but it looks like there's a lot 'baked in' there: styles, UI stuff, etc. If markdown isn't a possibility, perhaps a simplified 'semantic tags' only HTML version might be do-able?

Just a heads-up: there are still a number of Dropbox-hosted blog posts and guides out there that talk about markdown export, with no mention of deprecation. Might be good to add some notes to prevent confusion.

[Greg-DB]

Thanks for the feedback! I'll send this along as well.

[bram_l]

+1

I'm suprised this feature has dissapeared without any mentioning of it in the Paper Migration Guide. For us the Markdown export is an essential feature that would prevent us from using the 'paper_as_files' account in our current API integration.

Markdown is supported by wide a range of tools and libraries, thanks to its simplicity and well defined syntax. Therefor it seems much more appropriate as an export format for the API compared to HTML. Also converting Markdown to HTML (and applying styles) is very straight forward, the other way around not so much.

Hopefully this feature can be (re)implemented in the near future!

[Greg-DB]

@bram_l Thanks for the additional feedback! I'll pass this along as well.

[htbsrvr]

This is a deal breaker for our integration. Please add this feature!

[Greg-DB]

@htbsrvr Thanks for the note!

[entotto]

+1 - being able to export in a machine-readable format will be useful for automation: we could do all sorts of things like readability checks or validation of conformance to a required format.

It will also be useful to be able to import paper docs in Markdown from, say, a source repository that's managed and reviewed internally, and use them as templates, for example. (I know this is a different feature request, sorry for piggybacking here.)

[euxn]

Any Update?