Add a WhatsApp account

Writes what this market declares for compliance, and answers with the market as stored — the same shape `GET` on this path returns, so **what comes back can be sent back**. ## Partial, at every level **An omitted key is left alone. An explicit `null` clears it.** Those are different requests, so `{}` changes nothing and is refused rather than silently accepted, and correcting one field does not blank the others. ```json { "compliance": { "brand": { "contact_phone": "+12125550123" } } } ``` That leaves the campaign untouched, along with every other field of the identity. ## What a US `TEN_DLC` market holds Two halves, both singular: `brand`, the identity the registration is filed against, and `campaign`, the programme filed against it. Each carries `inherit`. | Body | Effect | | --- | --- | | `"brand": { … }` | supplies or corrects the identity, and takes one of your own | | `"brand": { "inherit": true }` | runs on your organization's, giving up your own | | `"brand": null` | the same thing, said the short way | | `"campaign": { … }` | supplies or corrects the programme, and takes one of your own | | `"campaign": { "inherit": true }` | runs on your organization's | | key omitted | left exactly as it is | **Nothing here creates a second anything.** One identity and one campaign per market, so a write is an upsert and a replayed request lands on the row it already wrote. Sending the campaign twice does not file two registrations. ## Every other market Markets that register with no regime have neither half — their compliance is documents, which cannot be JSON values and are sent as multipart on `POST /v3/channels/sms`. Only US `TEN_DLC` registers, so this path is `404` everywhere else. ## What it will refuse **A filed identity is `409`.** Once the registration has gone to The Campaign Registry they hold a copy, and a local change would diverge from it silently. The campaign is not frozen — omit `brand` and the same body is accepted. **More than one campaign is `409`.** The schema permits several and an account built on the admin side may hold them; this surface writes one, and editing whichever sorted first would leave the others unmentioned and unedited. Nothing is submitted to a regime here. These are the rows a submission is later assembled from, which is what lets them be corrected without waiting on something externally rejectable. Send `x-profile-id` with an organization key to write one of your profiles' markets.