Meta Graph API - Application Connected Client Businesses | Developer Documentation

Review which customer each connection serves

Use this checklist when your own service connects several businesses through ChatArchitect. A customer's workspace in your application, a Meta business portfolio and a ChatArchitect connection are different records. A list of businesses connected to a Meta app is not your application's customer-access rule.

Write down the mapping your service actually uses

• The customer or workspace in your service and the person responsible for its connection.
• The intended business number and the connection selected in that workspace.
• A reference to the issued credential pair in your server-side configuration; keep Secret values out of this inventory.
• The incoming-message receiver and the conversation where that workspace should see replies.

The identifier guide explains which account references to keep. Use the credentials guide for App key/App ID and Secret. Do not infer that one key always represents one number or portfolio; confirm the scope of the actual issued connection.

Check the boundary between two workspaces

1. Select an authorized test workspace and confirm the connection shown before sending.
2. Use a permitted contact and follow the API preparation guide and the Quick Start for a small outgoing/incoming test.
3. Check that the request used the intended server-side credential reference and that its result and reply appear in the intended workspace.
4. Repeat for another authorized workspace. Check that the first workspace cannot select that customer's connection or display its conversation through your application's normal permissions.

This is an acceptance check of your application, not a documented ChatArchitect tenant-isolation endpoint. Shared receiver and multi-number arrangements need an explicit, verified mapping; the Quick Start does not define every callback or routing field.

When a reply or sending result reaches the wrong workspace

Keep the workspace references, business number, time and available request/event references. Check your configuration and number-routing inventory before changing the established receiver. Use delivery results for the attempt, and ask support to clarify any unconfirmed connection scope. Do not copy another customer's credentials to make a missing connection appear.