MB SuiteMB Suite
Menu

API reference · Dashboards

Cross-account Explorer views

dashboards · cross_account_explorer_views · 7 operations

GET/v1/dashboards/cross-account-explorer-viewsGET/v1/dashboards/cross-account-explorer-views/{view_id}POST/v1/dashboards/cross-account-explorer-viewsPATCH/v1/dashboards/cross-account-explorer-views/{view_id}POST/v1/dashboards/cross-account-explorer-views/{view_id}/duplicatePOST/v1/dashboards/cross-account-explorer-views/reorderDELETE/v1/dashboards/cross-account-explorer-views/{view_id}
GET/v1/dashboards/cross-account-explorer-views

List cross-account explorer views

dashboards.cross_account_explorer_views.list

ReadIdempotentSince 2026-11-01

Lists the workspace's saved cross-account Explorer views (tables whose rows break down every account of the workspace), in their manual order, paginated by cursor. An account (child organization) has none: the list comes back empty. It does not return data.

Scope
dashboards:read
Permission
View the module
MCP tool
dashboards_cross_account_explorer_views_listOn the full surface; on the compact one, mb_execute_operation with id: "dashboards.cross_account_explorer_views.list".

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

Parameters

limitintegerqueryoptional

How many views per page (default 50, at most 200).

Default: 50

cursorstringqueryoptional

The next_cursor of the previous page, to get the next one; omit it for the first page.

Response

dataarray<object>
has_moreboolean
next_cursorstring

Errors

invalid_inputunknown_fieldauthentication_requiredscope_insufficientmodule_access_deniedoperation_not_foundrate_limitedquota_exceeded

Example

curl "https://api.mb-suite.com/v1/dashboards/cross-account-explorer-views" \
  -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/dashboards/cross-account-explorer-views" \
  -H "Authorization: Bearer $MB_TEST_KEY"
GET/v1/dashboards/cross-account-explorer-views/{view_id}

Get one cross-account explorer view

dashboards.cross_account_explorer_views.get

ReadIdempotentSince 2026-11-01

Returns a saved cross-account Explorer view of the workspace with its name, date range and tables (single-platform tables; rows are broken down by account). Not found if the id does not exist in this workspace.

Scope
dashboards:read
Permission
View the module
MCP tool
dashboards_cross_account_explorer_views_getOn the full surface; on the compact one, mb_execute_operation with id: "dashboards.cross_account_explorer_views.get".

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

Parameters

view_idstringpathrequired

The view id (its list operation).

Response

idstring

View id.

namestring

Name.

moduleenum

analytics (Explorer) or crm (a CRM report).

Values: analytics, crm

layoutenum

stack or grid.

Values: stack, grid

date_rangeobject | null

The view's period.

tablesarray<object>

Its tables, KPIs and charts.

ordernumber | null

Manual order in its list.

is_favoriteboolean

Marked as favorite.

created_atnumber | null

Created (epoch ms).

updated_atnumber | null

Last edited (epoch ms).

created_bystring | null

Uid of who created it.

created_by_namestring | null

Their name («MB Suite» for the system).

Errors

cross_account_explorer_view_not_foundinvalid_inputunknown_fieldauthentication_requiredscope_insufficientmodule_access_deniedoperation_not_foundrate_limitedquota_exceeded

Example

curl "https://api.mb-suite.com/v1/dashboards/cross-account-explorer-views/{view_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/dashboards/cross-account-explorer-views/{view_id}" \
  -H "Authorization: Bearer $MB_TEST_KEY"
POST/v1/dashboards/cross-account-explorer-views

Save a new cross-account explorer view

dashboards.cross_account_explorer_views.create

WriteSince 2026-11-01

Saves a new cross-account Explorer view in the workspace with a name, date range (default last 30 days) and its tables (single-platform: type single with platform, dimensions, metrics, filters, sorts, column_widths, custom_labels, density, heatmap_mode; a multi table is cross_account_table_single_platform). Platforms, metrics, dimensions, filter operators and the preset are checked as in dashboards.explorer_views.create. Only a workspace (agency) organization can have them. Returns the new view id. Requires edit access to Dashboards.

Scope
dashboards:write
Permission
Edit in the module
MCP tool
dashboards_cross_account_explorer_views_createOn the full surface; on the compact one, mb_execute_operation with id: "dashboards.cross_account_explorer_views.create".

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

Parameters

namestringbodyrequired

View name.

date_rangeobjectbodyoptional

The view's period; default the last 30 days (type preset, preset_key last_30_days).

tablesarray<object>bodyoptional

The tables of the view: each one single-platform (type single with its platform).

Response

view_idstring

The new view's id.

Errors

invalid_inputunknown_fieldauthentication_requiredscope_insufficientcrm_action_deniedidempotency_key_reusedrate_limitedquota_exceeded

Example

curl -X POST "https://api.mb-suite.com/v1/dashboards/cross-account-explorer-views" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "name": "NAME"
}'

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 -X POST "https://api.mb-suite.com/v1/dashboards/cross-account-explorer-views" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "name": "NAME"
}'
PATCH/v1/dashboards/cross-account-explorer-views/{view_id}

Update a cross-account explorer view

dashboards.cross_account_explorer_views.update

WriteIdempotentSince 2026-11-01

Updates the name, date range and/or the full list of tables of a cross-account Explorer view of the workspace. Returns the updated view. Requires edit access to Dashboards.

Scope
dashboards:write
Permission
Edit in the module
MCP tool
dashboards_cross_account_explorer_views_updateOn the full surface; on the compact one, mb_execute_operation with id: "dashboards.cross_account_explorer_views.update".

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

Parameters

view_idstringpathrequired

The view id (its list operation).

namestringbodyoptional

New name.

date_rangeobjectbodyoptional

New period.

tablesarray<object>bodyoptional

All the tables (replaces the list); each one single-platform.

Response

viewobject

The view as saved.

Errors

cross_account_explorer_view_not_foundinvalid_inputunknown_fieldauthentication_requiredscope_insufficientcrm_action_deniedidempotency_key_reusedrate_limitedquota_exceeded

Example

curl -X PATCH "https://api.mb-suite.com/v1/dashboards/cross-account-explorer-views/{view_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 -X PATCH "https://api.mb-suite.com/v1/dashboards/cross-account-explorer-views/{view_id}" \
  -H "Authorization: Bearer $MB_TEST_KEY"
POST/v1/dashboards/cross-account-explorer-views/{view_id}/duplicate

Duplicate a cross-account explorer view

dashboards.cross_account_explorer_views.duplicate

WriteSince 2026-11-01

Copies a cross-account Explorer view into a new one titled '<name> (Copia)' with the same date range and tables. Returns the new view id. Requires edit access to Dashboards.

Scope
dashboards:write
Permission
Edit in the module
MCP tool
dashboards_cross_account_explorer_views_duplicateOn the full surface; on the compact one, mb_execute_operation with id: "dashboards.cross_account_explorer_views.duplicate".

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

Parameters

view_idstringpathrequired

The view id (its list operation).

Response

view_idstring

The new view's id.

Errors

cross_account_explorer_view_not_foundinvalid_inputunknown_fieldauthentication_requiredscope_insufficientcrm_action_deniedidempotency_key_reusedrate_limitedquota_exceeded

Example

curl -X POST "https://api.mb-suite.com/v1/dashboards/cross-account-explorer-views/{view_id}/duplicate" \
  -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 -X POST "https://api.mb-suite.com/v1/dashboards/cross-account-explorer-views/{view_id}/duplicate" \
  -H "Authorization: Bearer $MB_TEST_KEY"
POST/v1/dashboards/cross-account-explorer-views/reorder

Reorder cross-account explorer views

dashboards.cross_account_explorer_views.reorder

WriteIdempotentSince 2026-11-01

Sets the manual order of the workspace's cross-account Explorer views: pass their ids in the new order; every id must exist. Requires edit access to Dashboards in the workspace.

Scope
dashboards:write
Permission
Edit in the module
MCP tool
dashboards_cross_account_explorer_views_reorderOn the full surface; on the compact one, mb_execute_operation with id: "dashboards.cross_account_explorer_views.reorder".

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

Parameters

view_idsarray<string>bodyrequired

The ids of ONE list (Explorer views or CRM reports, not both) in the new order.

Response

countnumber

How many views were ordered.

changednumber

How many of them moved (only those are written), like dashboards.dashboards.reorder.

Errors

invalid_inputunknown_fieldauthentication_requiredscope_insufficientcrm_action_deniedidempotency_key_reusedrate_limitedquota_exceeded

Example

curl -X POST "https://api.mb-suite.com/v1/dashboards/cross-account-explorer-views/reorder" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "view_ids": [
    "VIEW_ID"
  ]
}'

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 -X POST "https://api.mb-suite.com/v1/dashboards/cross-account-explorer-views/reorder" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "view_ids": [
    "VIEW_ID"
  ]
}'
DELETE/v1/dashboards/cross-account-explorer-views/{view_id}

Delete a cross-account explorer view

dashboards.cross_account_explorer_views.delete

IrreversibleSince 2026-11-01

Deletes a cross-account Explorer view of the workspace. It goes to the 30-day trash. Outside the screen it requires a dry run and a confirm_token, except a plain REST DELETE with a key allowed to delete. Requires edit access to Dashboards.

With an API key, this DELETE runs directly: the record stays 30 days in the trash and the response carries its trash_item_id. With an OAuth token, and through the MCP, it needs dry_run → confirm_token.

Scope
dashboards:write and “Allow deletions” (dashboards:delete in OAuth)
Permission
Edit in the module
MCP tool
dashboards_cross_account_explorer_views_deleteOn the full surface; on the compact one, mb_execute_operation with id: "dashboards.cross_account_explorer_views.delete".

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

Parameters

view_idstringpathrequired

The view id (its list operation).

Response

oktrue
trash_item_idstring

The trash item this deletion left: the item_id of platform.trash.restore (POST /trash/{item_id}/restore). Missing if nothing went to the trash.

trash_item_idsarray<string>

Only when the deletion left more than one copy: all of them, the first being trash_item_id.

trash_expires_atnumber

When the copy leaves the trash for good (epoch ms): 30 days after the deletion.

Errors

cross_account_explorer_view_not_founddelete_not_allowedconfirmation_requiredinvalid_inputunknown_fieldauthentication_requiredscope_insufficientcrm_action_deniedidempotency_key_reusedrate_limitedquota_exceeded

Example

curl -X DELETE "https://api.mb-suite.com/v1/dashboards/cross-account-explorer-views/{view_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 -X DELETE "https://api.mb-suite.com/v1/dashboards/cross-account-explorer-views/{view_id}" \
  -H "Authorization: Bearer $MB_TEST_KEY"