history webhook reference | Developer Documentation

Check WhatsApp Business app chat history in ChatArchitect

When connecting an existing WhatsApp Business app number to ChatArchitect, decide which earlier conversations your team needs in the receiving CRM or help desk. Keeping the app active on the number does not establish that its earlier chats will be imported into that tool.

Use the coexistence guide for the connection workflow. The ChatArchitect API quick start does not specify history callbacks, an import command or a universal history-progress display. Confirm availability and scope with support for the intended integration before relying on earlier chats.

Agree what the receiving tool should import

• Identify the business number and the exact CRM, help desk or custom application.
• Record whether you approved history sharing during the supported connection flow. Review that choice before making earlier customer conversations available to another system.
• Ask which date range, conversation types, message types and media the integration can import and how you will identify a completed or failed import.
• Confirm how earlier messages are matched to customers and distinguished from newly arriving messages.
• Check access and retention rules in the receiving system using the data-handling guide.

Meta's provider-side history interface separates approved sharing from declined sharing. It can deliver history in multiple parts, and media details can arrive separately. Its platform limits do not promise the same coverage or completion indicator in your ChatArchitect integration.

Review an available import

1. Confirm with support whether history import is available for this connection and which result your team should expect. For a custom application, obtain a redacted supported example and the message-reference, direction and completion rules.
2. Record the connection time, sharing choice and agreed coverage. Select a few non-sensitive conversations within that coverage for comparison.
3. Compare original message times, senders and content in the Business app with the receiving tool. Check a message sent by the business and one received from a customer.
4. Inspect attachments separately. A displayed message row does not prove that its file can be opened in the receiving tool.
5. Review the supported completion result and any missing items. A populated first conversation is insufficient to establish that the entire import finished.
6. Check that an imported message already present through another supported route does not appear twice or trigger a new business action.

In a custom application, use the import ordering and reference rules confirmed for ChatArchitect. Keep original message times distinct from import receipt times. Imported old messages should not trigger a fresh autoresponse or reopen tasks merely because they have just reached your receiver.

If history sharing was declined

A declined history-sharing choice is different from a failed import. Continue using the supported new-message workflow and ask support what options, if any, are available if your team later wants earlier chats. Do not repeatedly restart the connection to try to bypass the recorded choice.

When history appears incomplete

For support, provide the connection and integration version, onboarding time with time zone, sharing choice, expected coverage, observed completion result and a few redacted missing-item references. Keep the Business app account in place while the issue is investigated.

Check address-book synchronization and messages sent from the Business app as separate workflows. See Meta's history reference for the provider interface; implement only the history behavior confirmed for ChatArchitect.