Edit messages webhook reference | Developer Documentation

Check edited WhatsApp messages in ChatArchitect

A customer can correct a message after your team has already read it or created a task from it. If you use a WhatsApp Business app number together with ChatArchitect, check whether the correction reaches the connected CRM and how your team handles the changed information.

Meta's edit-event reference applies to WhatsApp Business app coexistence connections and describes edits made within 15 minutes of sending. ChatArchitect supports keeping the Business app on the same number, as explained in the coexistence guide. That support alone does not establish forwarding or display of message edits.

The ChatArchitect API quick start does not specify edit callbacks, target-message mapping or automatic CRM corrections. Confirm these details for the actual connection before implementing a handler.

Match the correction to the original message

Meta distinguishes the edit event's own reference from the original message being edited. Obtain the corresponding ChatArchitect fields and matching rule from support before applying this distinction in your receiver.

• Check the connected business number, customer conversation and original message reference together.
• Preserve the original receipt and the correction according to your application's data policy. Make the current text and the fact that it was edited clear to the agent.
• If the target is missing or ambiguous, keep the correction for review instead of attaching it to the customer's most recent message.
• Review any task, address or order already created from the old text. A chat update alone does not update the business action your team took earlier.

For a media caption correction, confirm which changed values the integration provides. Do not treat a revised caption as proof that the attachment itself was replaced.

Check the receiving route with a permitted test

1. Confirm that the business number uses coexistence and that the receiving integration supports edit updates. Keep the Business app account connected while checking the behavior.
2. For a custom application, obtain a redacted edit example, target-message reference, revision or ordering rules and duplicate-handling requirements. Use the webhook overview for receiver and correlation checks.
3. From a permitted test account, send a harmless text to the business number. Compare the original message in the Business app and the receiving tool using the incoming-text checklist.
4. Edit that test text using the WhatsApp action while it is available. Record the original and edit times with time zone and the references exposed by the supported route.
5. Compare the corrected text on the phone with the receiving event, conversation display and any local record. Inspect these as separate stages.
6. If the supported contract permits replay in a test environment, verify that the same update does not create another chat item or repeat a business action.

When a correction is absent or misapplied

If edit updates are unavailable in the connected tool, ask the customer to send an explicit correction as a new text message. Confirm which instruction the team should follow before completing the affected task. Use the callback troubleshooting guide when the supported receiver is missing an expected event.

For support, provide the connection and integration version, test times, original/edit references if available, and the stage where the corrected text stopped appearing. Redact customer content using the data-handling guide. See Meta's edit-event reference for the platform interface; use the format confirmed for ChatArchitect.