I need to send a Calendar file (ICS) from the REST Api but i can`t.

Nevertheless, I could send a jpg file. In this article Twilio staff announced that users can send images and videos, but also PDFs, text files, and audio files using the Twilio API for WhatsApp.

This is my call with JPG file that attach the media in a whatsapp message OK:

curl -X POST \ https://api.twilio.com/2010-04-01/Accounts/ACYYYYYYYYYYYYYYYYY/Messages.json \ -H 'authorization: Basic  XXXXXXXXXXXXX' \ -H 'cache-control: no-cache' \ -H 'content-type: application/x-www-form-urlencoded' \ -H 'postman-token: 58fa6aca-3b92-66d4-f675-9906bed37302' \ -d 'To=whatsapp%3A%2BXXXXXXXX&From=whatsapp%3A%2BYYYYYYY&Body=Hola%20probando2&MediaUrl=https%3A%2F%2Flh4.googleusercontent.com%2F-nbafRpNzZAc%2FWjHLp8y3NOI%2FAAAAAAAAAAA%2Fc8CSoPlcgcAazvZFKSU3uYxwo3HZ7FVewCOQCEAE%2Fs128-c-k%2Fphoto.jpg%0A' 

When i substitute MediaUrl path with a txt file path or ics file, the message wasn't attach the file:

for example something like this:

curl -X POST \ https://api.twilio.com/2010-04-01/Accounts/ACYYYYYYYYYYYYYYYYY/Messages.json \ -H 'authorization: Basic  XXXXXXXXXXXXX' \ -H 'cache-control: no-cache' \ -H 'content-type: application/x-www-form-urlencoded' \ -H 'postman-token: 58fa6aca-3b92-66d4-f675-9906bed37302' \ -d 'To=whatsapp%3A%2BXXXXXXXX&From=whatsapp%3A%2BYYYYYYY&Body=Hola%20probando2&MediaUrl=https:%2F%2Faaa.bbb.com%2Fccc%2Fcalendar.ics%0A' 

One of my project , my security team asking me to share the whatsapp business api docker images hash values to promote docker images to our own docker repository.

These values i couldn't find in facebook whatsapp documentation .

After pulling the images i can get the hash values but security team wants to compare the downloaded one is the proper one or not .

  docker.whatsapp.biz/coreapp   docker.whatsapp.biz/web 

How can i access the whatsapp business api docker repository in internet ? Any lead ?

I am trying to make a WhatsApp bot inspired by the functioning of Discord bots, the bot will work in WhatsApp groups.

I have looked up the official WhatsApp Business API but I am not sure that they will not approve my number as it is just a hobby project and not a proper "business".

There is an alternative though and that is the Twilio WhatsApp API. However, they provide you with a sandbox. I can interact with it in DMs but as the sandbox number is a business account, I cannot add it to a group like discord.

I intend to write a server in python or node.

Can anyone share a solution or workaround? Only if I could add the Twilio number to a group my problem will be solved. Though I am ready to use any other API/Solutions for this.

We just deploy on AWS Cloudformation an enterprise WhatsApp API following the next instructions:

AWS WhatsApp API

So all works normally, and the deploy finished correctly, the problem comes with the option "SSL Configuration", we understand that the API creates a self signed certificate so we get the error on the browsers because of that.

The documentation says that we need to upload a certificate authority, but do we need to get one from a third party to avoid this error?

We are a little bit lost, any advice will be nice.

Currently i am working on whatsapp business api setup using docker . I have followed the instructions specified in installation document.

Installation done successfully and all containers are running fine. When i am performing the health check getting the below response

{     "health": {         "192.168.99.124:337e5a74fec8": {             "gateway_status": "unregistered",             "role": "primary_master"         },         "192.168.99.125:f6d56ce7a303": {             "errors": [                 {                     "code": 1011,                     "title": "Service not ready",                     "details": "Wacore is not instantiated. Please check wacore log for details."                 }             ]         },         "192.168.99.125:f18358cd1dff": {             "errors": [                 {                     "code": 1011,                     "title": "Service not ready",                     "details": "Wacore is not instantiated. Please check wacore log for details."                 }             ]         }     },     "meta": {         "version": "v2.25.5",         "api_status": "stable"     } } 

Two of the core containers (master and wacore) not getting instantiated. i verified my containers, all are running .

Does any one faced this issue ? or this one is the normal because response always giving 200 status code .