WhatsApp Business Account Solutions List API | Developer Documentation
Identify what a provider relationship record actually describes
An application or partner-solution list describes a particular administrative view. It is not a list of the customer's ChatArchitect sending tools, API credentials or message destinations. If someone supplies such a record during setup or support, establish its source and scope before using it to diagnose the connection.
Prepare a record that can be compared
| Detail | Question to resolve |
|---|---|
| Source and date | Who supplied the record, from which system, and when was it observed? |
| Business/account | Which account or business identifiers does it cover, and is that the account for the number being discussed? |
| Named company/application | What role does the named company or application have in the agreed setup? |
| Access or state | What does the visible label actually mean in that record, and who can confirm its consequences? |
| Customer question | Is the issue access, selecting an account, a proposed provider change, or an actual message result? |
Keep missing details as questions for the person who supplied the record. Do not merge an account ID, application ID, solution ID and business phone number into one identifier.
Use the record for the right decision
- For business access, compare it with the responsible administrator and asset record.
- For an account missing from signup, prepare the two-view comparison of the actual account and connection attempt.
- For tool-level sending or receiving, use the customer routing record and an observed message example; a provider-list label does not prove delivery.
- For an additional partner or proposed change, agree responsibilities and the change plan before changing access.
Ask support to reconcile the views
Provide the relevant number, redacted record, observation time and the customer outcome you are trying to explain. Ask which relationship is relevant to that outcome and which additional evidence is required. Do not send a Meta token or ChatArchitect Secret as part of the comparison.
The former Meta Solutions List API examples did not establish a supported customer endpoint in ChatArchitect. Customers use their issued ChatArchitect credentials and documented interface. The internal provider model and the meaning of an account-specific relationship require confirmation.
No comments to display
No comments to display