Parent BSUIDs are an optional identity layer for managed businesses with multiple business portfolios. They let enrolled portfolios use one parent-scoped identifier for the same WhatsApp user.
What Parent BSUIDs Are
A regular BSUID is scoped to one business portfolio. A parent BSUID is scoped to a parent BSUID account that contains multiple enrolled business portfolios.
Format:
US.ENT.11815799212886844830Parent BSUIDs function like regular BSUIDs for messaging, but can be used by any business phone number in the enrolled portfolio set.
Who Can Use Them
Meta's documentation describes this as an eligibility-based feature for managed businesses. If you have multiple business portfolios and need parent BSUIDs, ask your Meta point-of-contact to check eligibility and enrollment.
After enrollment:
- webhook payloads include both regular BSUIDs and parent BSUIDs;
- users are identified by the same parent BSUID across enrolled portfolios;
- each business portfolio keeps its own access control, billing, and administrative independence;
- all portfolios enrolled in the same parent BSUID account are visible to each other through the Parent BSUID Accounts API.
Payload Fields
Parent BSUIDs appear with field names such as:
| Field | Surface |
|---|---|
parent_user_id | Contacts blocks, incoming message contacts, user preferences, group participants, contact book-adjacent payloads. |
from_parent_user_id | Incoming messages and user-initiated calling payloads. |
recipient_parent_user_id | Message and call status webhooks. |
recipient_participant_parent_user_id | Group message status webhooks. |
to_parent_user_id | Business-initiated call and app-echo payloads. |
Only store these fields when present. Do not assume every customer or portfolio has parent BSUIDs enabled.
Parent BSUID Account API
Use the Parent BSUID Accounts API to identify the parent account and enrolled portfolios:
GET /<BUSINESS_ID>/parent-bsuid-accountsResponse shape:
{
"parent_bsuid_account_id": "<PARENT_BSUID_ACCOUNT_ID>",
"enrolled_business_portfolios": [
"<BUSINESS_PORTFOLIO_ID>",
"<BUSINESS_PORTFOLIO_ID>"
]
}parent_bsuid_account_id is the shared parent account. enrolled_business_portfolios lists the portfolio IDs allowed to use that account's parent BSUIDs.
Operational Rules
- Regular BSUIDs still work inside their original business portfolio.
- Parent BSUIDs can be used by phone numbers across the enrolled portfolios.
- Contact books remain scoped to individual business portfolios, even when portfolios share parent BSUIDs.
- CRM systems should store both regular BSUID and parent BSUID when both are present.
- Parent BSUID enrollment does not merge billing, permissions, or admin controls across portfolios.
Limitations
Parent BSUIDs are not supported everywhere:
- Contact Book API deletion requires a regular BSUID.
- Block and unblock user requests do not support parent BSUIDs.
- Payloads omit parent BSUID fields unless enrollment is enabled.
Check endpoint-specific docs before assuming parent BSUIDs are accepted.
Dualhook Boundary
Dualhook does not enroll portfolios into parent BSUID accounts and does not manage parent BSUID account membership. If your business is eligible, enrollment is handled through Meta.
For Dualhook Platform customers, tenant message-path webhooks still route Meta → tenant endpoint directly. Your tenant-side systems must capture parent_user_id fields if you need cross-portfolio identity.