I know that I can download a set of reports within a single dashboard in an Excel file with multiple sheets based on the number of reports through email. But my suggestion is whether we can do the same thing using an API. I’ve felt the need for this a lot recently, where I need to export the dashboard but through the API, and I hope it follows the same method and options as the email.
Note:
Not the canvas dashboard. I mean the normal dashboard if I can call it like that. Below an example
I need to be able using API to export the dashboard with 2 sheets based on the number of reports but not using email. I need to do it using API please.
See more details on how to export a widget at Get Data.
When the Job is finished, you can download the exported file using the download export API.
Exporting all reports from a dashboard into one single Excel file (with each report as a separate sheet) is currently not available via APIs.
That being said, I can definitely see how it can be a useful addition. Duly noted in our product backlog.
Let me get back to you when there’s an update. Cheers!
Bumping this feature since we’re looking for something similar, but in PDF format. I’m guessing that they’d likely be implemented together since the download widget API endpoint gives different format options?
Thanks for the response, but we would like to export the entire dashboard as a PDF via API rather than just one widget. That’s why I’m bumping this feature request for exporting the entire dashboard.
Hi @anya.conti,
Currently, our system does not support direct exports of the full dashboard via API. A workaround would be to set up a data schedule via API.
This will send a PDF to your nominated email address. Detailed instructions can be found in our Create Email Schedules using API tutorial. Given that exporting a full dashboard can be time-consuming—especially with numerous widgets—we recommend emailing or sending exported files to SFTP.
Ah, that’s helpful, thanks! That might work for us. It does feel a little messy, so definitely still want to bump this feature request. But in light of the workaround, not as high priority.