Pulse API Deprecation

Get Help
1

Hi Metabase Team,
We're about to start implementing automatic email reports of a different set of dashboards for our customers via the API, but looking through the documentation and the Github issues we stumbled upon the deprecation of the Pulse API in favor of DashboardSubscriptions.

What we found:

The API Docs show 2 different endpoints for creating subscriptions:

But there’s a few things missing in the Metabot (new) endpoint compared to the Pulse (old) endpoint

  • No list of recipients, just the 1 recipient
  • That recipient needs to be a valid user, if not, the creation fails
  • No way to filter the dashboards

Our questions are the following:

  • Is the Metabot API going to replace the Pulse API soon? If so, what’s the timeframe?
  • Is there going to be feature parity? Specifically regarding recipients and filters
  • When the Pulse API gets deprecated, will it be disabled or will it still work but unmaintained?

Thanks in advance!

2

use GitHub - paoliniluis/pulse-migrator: A script to migrate Metabase pulses to subscriptions and adapt, don’t worry about Metabot yet, that’s a work in progress

1 Like
3

Okay! Excellent, we’ll use the Pulse API then.

Thanks!!

4

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.