Sign in

Withhold content types and oversized media the whatsapp API cannot transmit

Before attempting a send, the composer checks the attachment against WhatsApp's capability declaration and blocks anything unsupported or oversized, with a clear reason, instead of letting the Cloud API reject it after the fact.

When this happens: Operator attaches a file to the composer.

Step by step

  1. 1

    Attaches a 22 MB video to a WhatsApp reply.

    EasyCRM checks it against the WhatsApp capability declaration (video ≤ 16 MB, FR-16-013). Withholds the attachment before send, showing This video is 22 MB; WhatsApp accepts up to 16 MB The Operator can compress it externally and re-attach, or send a different file.

Other paths

Unsupported mime type

Attaches a file type not in the capability declaration (e.g. An unsupported document format). Withholds it with WhatsApp cannot receive this file type, listing the supported document types.

If something goes wrong

Client check bypassed

A send request for unsupported/oversized content reaches the server despite the client-side check (e.g. A stale client). Rejects with EasyCrm:Channel:ContentTypeNotSupported before any provider call.

Good to know

  • Withholding happens before any Cloud API call — never a silent drop, never a provider-side failure surprise.
  • The platform's own upload allow-list may be narrower than WhatsApp's limits; the stricter of the two applies.