Migrating Metabase Data using the API

Here’s link to the beginnings of a tool written to migrate questions and dashboards to multiple instances:

Some specific API call experiences

Does the pameters go in as query string parameters or in the body. To URI encode — or not … that is always the question! If not the answer at least here are some of the experiences (including some answers):

We were hoping to use a single instance of Metabase for multiple tenants who have their own data source configured. The datasources will point to multiple database instances with the same schema. We wanted to create some questions and dashboards that will be common across all tenants, and give the flexibility for individual tenants to create their own questions/dashboards as well.
We wanted an easy way to create these common questions and dashboards in one place and be able to migrate these ove…

…
…

Finally - if you want/need to get rid of the Metabase logo (either to save precious screen space, want to “whitelabel” when you embed in your own product or service – or simply because you would like to support their endeavor) the Metabase guys have this offering called Premium Embedding which they wrote about here:

I’ve just lost a morning persuading JWT to work in .Net, so hopefully this will save someone else a load of bother! Maybe somebody has a simpler approach. If so, please let me know. The code below could very easily be abbreviated. I’ve kept it long-winded to make it easier to follow.
When you select the option to embed a dashboard in an application, you see some nice simple Node.js (or other) code. We can assume there’s an awful lot going on behind the scenes, because the C# code is much more w…