WhatsApp Cloud API - Business Encryption API | Developer Documentation
Encryption keys and ChatArchitect credentials
ChatArchitect has no customer setting for supplying or managing your own encryption key for WhatsApp or WhatsApp Flows. Do not plan a connection that depends on uploading a customer-managed message-encryption key through a ChatArchitect setting.
For a ChatArchitect integration, use the issued App key and Secret. Those credentials authenticate access to the integration. They are not a customer-managed payload-encryption or decryption key.
Keep the different key requirements separate
| Requirement | What to use or confirm |
|---|---|
| Authenticate a request to the ChatArchitect API | Follow the ChatArchitect API Quick Start with your App key and Secret. |
| Supply your own encryption key for WhatsApp or WhatsApp Flows | ChatArchitect has no customer setting for this. A Meta public-key example is not a ChatArchitect configuration procedure. |
| Establish which systems can access message content | Identify the connected CRM, help desk or custom application and obtain the relevant information from each system's owner. API credentials alone do not describe encryption across the whole connection. |
| Set retention or remove copies | Use the data-handling guide and the controls of systems that keep copies. Retention and encryption are separate properties. |
Check a security requirement before relying on it
Describe the requirement to your technical administrator: which data it covers, which participating systems may read it, and whether your organization must control a cryptographic key. Record the connected business number and the CRM/help desk or custom application involved.
For a requirement concerning ChatArchitect's actual processing or encryption arrangements, ask support to confirm that precise property and its scope. For storage, access and encryption inside a CRM or your own application, obtain the information from that system's owner. The absence of a customer key setting does not establish every encryption property of the participating systems.
Interpret the confirmed storage statement correctly
ChatArchitect does not store customer message texts or attachments. This does not establish retention in Meta or a connected CRM, deletion of exported copies, or the encryption properties of the complete route. Keep those questions separate in your security review.
Use the documented connection
Set up API authentication according to the Quick Start, and handle the Secret as an API credential. Do not substitute a Meta public or private key in the App key or Secret fields. If another guide asks you to upload an encryption key, identify the service and workflow it describes before changing a working connection.
The former imported Meta key-management reference did not define a customer key-management operation in ChatArchitect. The absence of a key setting also does not decide whether a separate WhatsApp Flows scenario is supported.
No comments to display
No comments to display