DELETE
/BizEntity/Parent
Usage Notes
When
- Dissolve fund family structures when sub-funds become independent
- Remove parent-child relationships after corporate demergers
- Clean up relationships when subsidiary entities are dissolved
Requirements
- Both child and parent entity identifiers required to target relationship
- No dependent relationships or active processes referencing the relationship
Notes
- Deletion is permanent with no recovery mechanism
- Only the relationship is removed - underlying entities remain intact
- Alternative: use PUT to set activeTo date for auditable termination
Description
Permanently removes a parent-child relationship while preserving underlying entities. Both entities remain active and can be assigned to new relationships.
Required Headers - See Authentication
| Header | Value | Description |
|---|---|---|
| Authorization | {accessToken} | Bearer token for API access |
| Version | 2.0 | API version identifier |
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
BizEntityID |
integer | Native 7G identifier for child entity in relationship deletion. Fastest deletion path using primary index. | |
ParentBizEntityID |
integer | Native 7G identifier for parent entity in relationship deletion. Optimal performance with native IDs. | |
ExternalBizEntityId |
string | External identifier for child entity. Enables relationship deletion via external references. | |
ExternalParentBizEntityId |
string | External identifier for parent entity. Supports dual-ID relationship dissolution. |
BizEntityID
Native 7G identifier for child entity in relationship deletion. Fastest deletion path using primary index.
ParentBizEntityID
Native 7G identifier for parent entity in relationship deletion. Optimal performance with native IDs.
ExternalBizEntityId
External identifier for child entity. Enables relationship deletion via external references.
ExternalParentBizEntityId
External identifier for parent entity. Supports dual-ID relationship dissolution.
🔗 Relationship Identification for Deletion
DELETE operations require precise identification of the parent-child relationship:
- Dual Identification: Both child and parent entity identifiers must be provided to uniquely identify the relationship
- ID Flexibility: Use native 7G IDs (BizEntityID, ParentBizEntityID) or your external IDs interchangeably
- Mixed ID Support: Can combine native ID for one entity with external ID for the other
- Precision Required: Wrong combination will result in 404 Not Found - relationship must exist exactly as specified
⚠️ Critical: Deletion is permanent and irreversible. Ensure the correct relationship is identified before proceeding. The system will validate dependencies and prevent deletion if business rules are violated.
Example Requests
bash
# Dissolve fund family - sub-fund becomes independent
curl -X DELETE 'https://api.7g.com.au/BizEntity/Parent?BizEntityID=12345&ParentBizEntityID=10001' \
-H 'Authorization: {accessToken}' \
-H 'Version: 2.0'
# Remove relationship using external identifiers
curl -X DELETE 'https://api.7g.com.au/BizEntity/Parent?ExternalBizEntityId=SUB-FUND-001&ExternalParentBizEntityId=MASTER-FUND-001' \
-H 'Authorization: {accessToken}' \
-H 'Version: 2.0'Response Examples
json
{
"result": true,
"message": null,
"recordCount": 0,
"data": null
}