Menu

API reference · Deliveries

Content

deliveries · content · 2 operations

GET/v1/deliveries/content/dashboards

List the dashboards a delivery can link to

deliveries.content.list_dashboards

ReadIdempotentSince 2026-11-01

Lists the dashboards of target_org_id (this organization or one of its accounts) that a delivery can link to, most recently updated first (up to 500): id (use it as resource_id of a dashboard_link content item), title, number of pages and widgets, and the platforms they show. Check deliveries.content.check_portal too: interactive links need the Client Portal. Errors: target_org_invalid (also for an account of this workspace that the caller is not assigned to). Requires view access to Deliveries.

Scope
deliveries:read
Permission
View the module
MCP tool
deliveries_content_list_dashboardsOn the full surface; on the compact one, mb_execute_operation with id: "deliveries.content.list_dashboards".

Declared cost: up to 1501 reads and 0 writes per call (they count against the daily quota).

Parameters

target_org_idstringqueryrequired

The account whose dashboards can be linked (or this organization itself): an id from platform.orgs.list.

Response

dataarray<object>

The dashboards, most recently updated first (up to 500).

Errors

Example

curl "https://api.mb-suite.com/v1/deliveries/content/dashboards?target_org_id=TARGET_ORG_ID" \
  -H "Authorization: Bearer $MB_API_KEY"

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl "https://api.mb-suite.com/v1/deliveries/content/dashboards?target_org_id=TARGET_ORG_ID" \
  -H "Authorization: Bearer $MB_TEST_KEY"
GET/v1/deliveries/content/portal-eligibility

Check whether deliveries can link to dashboards

deliveries.content.check_portal

ReadIdempotentSince 2026-11-01

Says whether deliveries can include interactive links to dashboards: they open in the workspace's Client Portal, so it needs a portal slug and the Client Portal module on (on the parent workspace when called from an account). Returns eligible, the portal_slug, and the reason (in Spanish, as the screen shows it) when not eligible. Optional target_org_id checks the caller's access to that account. Requires view access to Deliveries.

Scope
deliveries:read
Permission
View the module
MCP tool
deliveries_content_check_portalOn the full surface; on the compact one, mb_execute_operation with id: "deliveries.content.check_portal".

Declared cost: up to 2 reads and 0 writes per call (they count against the daily quota).

Parameters

target_org_idstringqueryoptional

Optional: the account the links would point to (checked against your access to it).

Response

eligibleboolean

Whether deliveries can carry dashboard links.

reasonstring

Why not (in Spanish, as the screen shows it).

portal_slugstring

The Client Portal slug the links use.

Errors

Example

curl "https://api.mb-suite.com/v1/deliveries/content/portal-eligibility" \
  -H "Authorization: Bearer $MB_API_KEY"

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl "https://api.mb-suite.com/v1/deliveries/content/portal-eligibility" \
  -H "Authorization: Bearer $MB_TEST_KEY"