Security Center allows organizations to manage relationships between a parent (master) org and one or more child orgs through Security Hub. When these relationships need to be removed, the Salesforce REST API provides dedicated endpoints to disconnect orgs programmatically. For example, an administrator may need to remove a child org from a Security Center tenant or detach a child org from its parent org entirely. Each disconnect operation must be executed from the correct org either the parent or the child — depending on which side of the relationship you are acting on.
master-org, masterOrgId). This document uses parent in explanations and master where it matches the API.child-org, childOrgId).|
What you want to do
|
Run the API from this org
|
|---|---|
|
Remove a child from the relationship (disconnect a specific child from the parent)
|
Parent org
|
|
Remove the parent from the relationship (disconnect this org from its parent)
|
Child org
|
The following REST API calls can be used to manage Security Hub org relationships. All calls require API version 224 or newer.
Get Org Relationships (Call from the Org You Want to Inspect):
Use this to read which Security Hub org relationships exist for the currently authenticated org. The response lists relationship records from that org's perspective (for example, links to a parent or to children), so you can confirm who is connected before making any changes.
HTTP method: GET
Path (after your instance base URL): /services/data/v{apiVersion}/connect/securityhub/org-relationships
Query Parameters: None
Example:GET https://{yourInstance}/services/data/v62.0/connect/securityhub/org-relationships
Requires API version 224 or newer (for example, v62.0 is valid).
Disconnect a Child Org (Call from the Parent Org):
Use this when you are logged into or authenticated as the parent org and want to stop that parent's relationship to a given child org.
HTTP method: DELETE
Path (after your instance base URL): /services/data/v66.0/connect/securityhub/master-org?masterOrgId=<ParentOrgId>
Query Parameters:
| Parameter | Description |
|---|---|
childOrgId | The Salesforce org ID of the child org you are disconnecting from this parent. |
bidirectional | true — also update the child org so it no longer lists this org as its parent (coordinated disconnect). false — only perform the disconnect from the parent side; the child org is not updated in that coordinated step. |
Examples:
Coordinated disconnect (parent and child both updated when possible):DELETE https://{yourInstance}/services/data/v65.0/connect/securityhub/child-org?childOrgId=00Dxxxxxxxxxxxxxxx&bidirectional=true
Parent-side only:DELETE https://{yourInstance}/services/data/v65.0/connect/securityhub/child-org?childOrgId=00Dxxxxxxxxxxxxxxx&bidirectional=false
Use API version 224 or newer (replace v65.0 with the version your integration uses).
Disconnect the Parent Org (Call from the Child Org):
Use this when you are logged into or authenticated as the child org and want to remove its link to the parent org.
HTTP method: DELETE
Path (after your instance base URL): /services/data/v{apiVersion}/connect/securityhub/master-org
Query Parameters:
| Parameter | Description |
|---|---|
masterOrgId | The Salesforce org ID of the parent (master) org you are disconnecting from. |
Example:DELETE https://{yourInstance}/services/data/v65.0/connect/securityhub/master-org?masterOrgId=00Dxxxxxxxxxxxxxxx
This operation does not use a bidirectional parameter. Use API version 224 or newer.
Base URL Structure:
REST calls use your org's Salesforce instance and the standard REST API prefix, for example:https://{instance}/services/data/v{apiVersion}/connect/securityhub/...
The org in the URL and token must match the org from which you are making the call (parent or child, as described above).
005318666

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.