Hi Dylan (and others),
Additional info, as it pertains to Dropbox api calls to display html content. Here’s the explanation from Dropbox support.
The Dropbox API only offers an interface for programmatically interacting with files and folders, such as to list the contents of a folder, or download the data of a file. It does not offer UI, such as the UI for a text editor or an HTML viewer.
The Dropbox mobile apps use the API to get the file/folder metadata/data, and then present that information in relevant UI, such as a text editor or HTML viewer. Specifically, to download a file, it would call /2/files/download. Then, it would pass the downloaded data to the relevant UI component. For instance, for a .html file, it may offer the option to open that data in an HTML viewer.
If you want to replicate that sort of user experience in your own integration, you would need to implement the same sort of thing. That is, you could call /2/files/download to get the raw data for a .html file, and then you would need to pass that data into some HTML viewer. The Dropbox API doesn’t offer an HTML viewer though, so I can’t offer help on that particular step of the process. You may want to refer to the documentation for whatever platform/operating system you’re working in to see what options, if any, it offers for rendering HTML.
In essence, Dropbox api only offers the ability to download the content. That’s the reason I was looking into the browserless.io options. Just thought I would provide some updates as I continue to research a solution for this dilemma.
Scott.