waba-embedded-signuplisted

# WABA Onboarding and Embedded Signup Keep three integration paths distinct. Calling all of them “Embedded Signup” creates wrong API designs and unsafe credential handling. ## The three paths | Path | Where it starts | Profile behavior | | --- | --- | --- | | Organization Embedded Signup | Sent dashboard | Connects the organization's WABA through the hosted Meta flow. There is no public Sent endpoint that starts this flow. | | Organization WABA inheritance | `POST /v3/profiles` | Omit `whatsapp_business_account`; the child inherits the organization's connected WABA. | | Dedicated child-profile WABA | `POST /v3/profiles` | Supply `whatsapp_business_account.waba_id` and `.access_token`; `phone_number_id` is optional. | If credentials are omitted and the organization has no connected WABA, profile creation returns `422`. Direct WABA credentials are a profile-creation feature, not a public “Embedded Signup endpoint.” ## Authentication Use either: - a profile-specific key in `x-api-key`; or - an organization key in `x-api-key` plus `x-profile-id` when operating for an existing child profile. Only organization keys may use `x-profile-id`; profile keys receive `403`. `x-sender-id` is legacy v1/v2 terminology. ## Path A: organization Embedded Signup 1. An authorized organization administrator opens the Sent dashboard WhatsApp connection flow. 2. The hosted Meta Embedded Signup UI collects the Meta authorization and WABA/number choices. 3. Confirm the organization shows a co