WhatsApp Cloud API - Media API | Developer Documentation

Find and manage the copies of a WhatsApp attachment

ChatArchitect does not store customer message texts or attachments. To find, restrict or remove an existing attachment, identify the application or storage location that holds the copy. The data-handling guide separates ChatArchitect, Meta, your connected application and your team's own copies.

Identify the copy you are working with

• Conversation attachment: open the original message in the connected CRM or help desk and check its file controls and access permissions.
• Downloaded file: identify the computer, shared drive or other location where your team saved it.
• Export or screenshot: check the export destination and the systems where your team copied the record.
• A Meta or WhatsApp operation: use that service's current instructions and confirm which object or copy the operation affects.

Confirm the scope before changing access or deleting a file

1. Match the customer, message and exact attachment. Make sure that you are acting on the intended copy.
2. Ask the relevant administrator what its access, retention and deletion controls do. Confirm who can perform the operation and which record it affects.
3. If your team needs to keep a copy, follow your own approved storage process before removing the record from that location.
4. After the action, check that location using the permissions of the intended account. Check other known copies separately.

Removing a file from one application does not establish the state of copies on another platform or in the recipient's conversation. This guide does not promise deletion from every system.

If the attachment is missing or an API is needed

Use the download troubleshooting checklist to distinguish access errors, link problems and unavailable files. For new attachments, use the file preparation guide.

The ChatArchitect Quick Start does not specify media-delete endpoints or media-ID lifetimes. Obtain a current contract for the requested operation before writing a custom client. The former imported Meta Media API was a separate technical reference; its Bearer-token requests do not define a customer operation in ChatArchitect.