WhatsApp Business Pre-Verified Phone Number Partners API | Developer Documentation
Check an access request for a verified WhatsApp number
Someone may ask for business access while describing a WhatsApp number as already verified or shared with a partner. Establish which action is requested. Confirming control of a telephone number, identifying an existing partner relationship and granting access are separate questions.
ChatArchitect customers follow the supplied connection flow. The former Meta pre-verified-number partner-list reference does not define a customer API for granting access or requesting a verification code.
Identify what you have been asked to do
| Request or observation | Next check |
|---|---|
| A setup screen asks for an SMS or voice code | Check that the screen belongs to the connection you intended to start and displays the intended number. Use the number verification guide. This step concerns control of the number; it is not a partner-list lookup. |
| A company is named in a partner record | Keep the record's source, account or number reference and observation time. Use the provider-record guide to establish what that administrative view describes. |
| You are asked to grant, change or remove business access | Identify the requester, intended business asset and specific requested role or action. Have the business responsible for that asset confirm the purpose and supported procedure before changing access. |
| A partner name is used to explain a sending failure | Record the actual failed message direction, tool, time and result. A partner label alone does not establish whether an integration can send or receive. |
Prepare an access decision for the responsible business
- Record the telephone number, business portfolio and WhatsApp account being discussed. Label each reference; do not use a partner ID as a phone number.
- Ask the requester to explain the exact operation and the customer outcome: connection, access review, provider change or message troubleshooting.
- Compare that request with the existing setup and the person authorized to make the change. If a working app or provider is involved, use the existing-number change checklist to record what must continue working.
- Ask ChatArchitect support to clarify any special pre-verified or shared-number arrangement before applying it. The imported partner-list example does not establish availability of that arrangement through ChatArchitect.
A completed phone verification does not answer the access decision. Likewise, a relationship record is not permission to change the customer's business assets. Keep the two checks separate so the responsible business can approve the actual operation.
If the request and the setup do not match
Provide support with a redacted copy of the request or record, the relevant business number, the system it came from, observation time and the outcome you want to achieve. State whether the unresolved question is number verification, a named partner's role or a change to access. Include the exact screen or error when setup is blocked.
Do not put passwords, verification codes, PINs or Secret values in that comparison. Enter verification codes only in the intended setup step. Use App key and Secret for documented ChatArchitect API authentication; they are not credentials for the Meta partner-list endpoint.
No comments to display
No comments to display