WhatsApp Business - Assigned WhatsApp Business Accounts API | Developer Documentation
Compare the visible Meta account with the missing signup choice
Use this worksheet when the intended WhatsApp account is visible to an authorized person in Meta, but that same account cannot be selected in the supplied ChatArchitect connection form. First complete the ordinary business-access checks with the responsible administrator. This article prepares evidence for the remaining discrepancy; it does not repeat the access setup.
Record both views of the same attempt
| Item | What to record |
|---|---|
| Intended asset | The portfolio, WhatsApp account and business number, with available identifiers and their labels. Use the reference checklist; similar names alone are ambiguous. |
| Meta view | The signed-in user and selected portfolio, the screen where the account is visible, and the administrator's confirmation that it is the intended asset. Do not include a password or token. |
| ChatArchitect entry | How you opened the supplied connection, which tool/connection you intend to configure, and whether this is a new setup or a change to an existing service. |
| Connection-form view | The user/portfolio shown, exact step, visible account choices and any message. Distinguish a missing account from a visible account with a missing number or a later code-verification failure. |
| Time and recent changes | The attempt time with time zone and any confirmed relevant access/account change. Keep separate notes for attempts under different users or portfolios. |
| Evidence | Redacted screenshots of the two views and exact error text. Remove Secret values, tokens, one-time codes and unrelated private details. |
Ask support to identify the applicable route
Send the comparison and ask ChatArchitect support to confirm which connection route and prerequisites apply to this account and number. An account visible in Meta does not establish that every existing account is selectable in every supplied flow. Do not infer the cause from a Meta assigned-account API response or invent an eligibility rule from the missing choice.
If the number already has a provider or uses WhatsApp Business app, say so in the record. Use change planning before removing access or altering a working connection; the account's visibility does not establish a migration or recovery procedure.
Check the result after an agreed correction
Retry the supplied route after a confirmed correction. Compare the actual account and number selected with the recorded target, and retain the new step/result alongside the earlier attempt. Do not create a duplicate account merely to make an unexplained missing choice disappear.
If the form then completes, follow the connection completion checklist to verify the sending tool. If the account becomes selectable but a later step fails, record that new stage separately rather than treating it as the original visibility discrepancy.
No comments to display
No comments to display