Manage System Users | Developer Documentation

Use the credentials for your ChatArchitect connection

A custom service connected through ChatArchitect uses the App key/App ID and Secret supplied by ChatArchitect. The API quick start calls these credentials APP_ID and APP_SECRET and uses them as the Basic Auth username and password for ChatArchitect API requests.

Distinguish the account login and API credentials

For the regular ChatArchitect connection, customers do not create their own Meta System User access token to send requests directly to Meta Cloud API. Use the ChatArchitect API preparation guide to choose the supported interface.

Prepare the custom application

1. Confirm which connection and business number the issued credentials belong to.
2. Store both values on the server and use the API base URL and authentication shown in the current quick start.
3. Keep the Secret out of browser code, public repositories, screenshots and URLs.
4. Use a permitted test contact and record the sending result without copying the Secret into logs.

For a ready-made CRM or help desk, follow that integration's connection instructions. A Meta system-user permission list does not define the fields required by its setup form.

When authentication does not work

Check the destination API, selected connection and documented authentication format. An App ID copied from Meta Developers may have the same label but serves a different application. If the issued ChatArchitect pair is uncertain, ask support to identify the affected connection before changing working credentials.

Account selection issues belong to the signup completion checklist. Callback verification is a separate contract: use the webhook guide and confirm the receiver rules before treating outgoing API authentication as proof that an incoming event is genuine.

Provider implementation reference

For a separate Meta provider implementation, consult the Meta developer reference for Manage System Users. That reference uses its own application, account and permission context. Use the customer workflow above for ChatArchitect.