Menu

API reference · Integrations

Inherited connections

integrations · inheritance · 3 operations

GET/v1/integrations/inheritance

What an Account uses from its workspace

integrations.inheritance.list

ReadIdempotentSince 2026-11-01

In an Account, returns one row per platform that can be inherited (google_ads, meta_ads, google_analytics, tiktok_ads, tiktok, google_search_console, google_business_profile, facebook_page, instagram, linkedin_ads, linkedin_page, youtube, whatsapp_business): is_inherited (it is set to read that platform with the workspace's connection), parent_has_connection and credential_count (the workspace's connections that read the platform: Facebook and Instagram count Meta's, LinkedIn pages also LinkedIn Ads'), usable (both: it reads the platform with the workspace's connection today), inheritance_state (own: it connects its own; available: it gave the workspace permission and the workspace has not connected yet; active: it uses the workspace's), and how that connection is: account (platform_account_name/email), connected_email, connected_at, token_expires_at, status (active, or error when the workspace has to reconnect it) and auth_error, plus the granted permissions. In a workspace it returns an empty list. Requires view access to Integrations. With LinkedIn or TikTok, their terms limit it through the API and the MCP: what they do not allow answers 403 platform_terms_restricted, and their fields are left out of the response (the permissions guide lists what each platform allows).

Scope
integrations:read
Permission
View the module
MCP tool
integrations_inheritance_listOn the full surface; on the compact one, mb_execute_operation with id: "integrations.inheritance.list".

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

Parameters

No parameters.

Response

dataarray<object>
has_moreboolean
next_cursorstring

Errors

Example

curl "https://api.mb-suite.com/v1/integrations/inheritance" \
  -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/integrations/inheritance" \
  -H "Authorization: Bearer $MB_TEST_KEY"
POST/v1/integrations/accounts/{account_id}/platforms/{platform}/activate

Connect the workspace's connection in an Account

integrations.inheritance.activate

WriteIdempotentSince 2026-11-01

From a workspace, starts using its own connection of a platform in one of its Accounts (Connect on the Account's card): for an Account that pays for itself and made the platform available (inheritance_state available in integrations.inheritance.list). In an Account managed by the workspace the platform is already inherited and nothing changes (changed: false). The workspace needs an active connection of the platform (409 integration_not_connected, details.scope workspace) and the Account has to have made it available (409 platform_not_managed_by_workspace). Lead sources of the CRM paused for lack of a connection resume on their own. Owners and admins of the workspace only. Errors: 404 account_not_found.

Scope
integrations:write
Permission
Edit in the module · Only owner, admin
MCP tool
integrations_inheritance_activateOn the full surface; on the compact one, mb_execute_operation with id: "integrations.inheritance.activate".

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

Parameters

account_idstringpathrequired

An Account (client organization) of this workspace, as listed by platform.orgs.list.

platformenumpathrequired

The platform whose inheritance changes (integrations.inheritance.list lists them for the Account).

Response

account_idstring
platformstring
changedboolean
cleaned_platformsarray<string>
paused_lead_sourcesnumber

Errors

Example

curl -X POST "https://api.mb-suite.com/v1/integrations/accounts/{account_id}/platforms/{platform}/activate" \
  -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/integrations/accounts/{account_id}/platforms/{platform}/activate" \
  -H "Authorization: Bearer $MB_TEST_KEY"
POST/v1/integrations/accounts/{account_id}/platforms/{platform}/deactivate

Stop using the workspace's connection in an Account

integrations.inheritance.deactivate

WriteIdempotentSince 2026-11-01

From a workspace, stops using its connection of a platform in one of its Accounts (Disconnect on the Account's card): the platform stays managed by the workspace but disconnected, the Account's linked accounts of that platform (and of the platforms sharing its connection, like Facebook pages and Instagram with Meta) are unlinked, and the Account's CRM lead sources that depended on it are paused (they resume when it is connected again). The workspace's own connection is untouched. Owners and admins of the workspace only. Errors: 404 account_not_found, 409 platform_not_managed_by_workspace.

Scope
integrations:write
Permission
Edit in the module · Only owner, admin
MCP tool
integrations_inheritance_deactivateOn the full surface; on the compact one, mb_execute_operation with id: "integrations.inheritance.deactivate".

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

Parameters

account_idstringpathrequired

An Account (client organization) of this workspace, as listed by platform.orgs.list.

platformenumpathrequired

The platform whose inheritance changes (integrations.inheritance.list lists them for the Account).

Response

account_idstring
platformstring
changedboolean
cleaned_platformsarray<string>
paused_lead_sourcesnumber

Errors

Example

curl -X POST "https://api.mb-suite.com/v1/integrations/accounts/{account_id}/platforms/{platform}/deactivate" \
  -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/integrations/accounts/{account_id}/platforms/{platform}/deactivate" \
  -H "Authorization: Bearer $MB_TEST_KEY"