Send a media file to a chat. Provide either mediaUrl (a publicly accessible URL) or mediaBase64 (base64-encoded file content with mediaName), but not both.
The chatId format varies depending on the chat type:
Forbidden — insufficient permissions or account blocked
404
Not found — instance does not exist or does not belong to you
409
Conflict — instance is not ready
422
Validation error — invalid or missing request parameters, or the send was refused before it was attempted. A send is refused when the recipient's number is not registered (override with skipNumberCheck: true), or when the connected account is under a reach-out restriction and this exact recipient has already been observed being rejected — contacts who replied are unaffected, and retrying counts towards the limit that caused the restriction. The message field names which of the two applies.
429
Refused by the instance's send protection. Nothing was sent; retry after the given number of seconds. Integrations that already handle 429 need no change.
Updated 8 months ago
Did this page help you?
Yes
No
Language
ShellNodeRubyPHPPython
Credentials
Bearer
JWT
Bearer
Loading…
Response
Click Try It! to start a request and see the response here! Or choose an example: