I have tried to send WhatsApp messages by twilio as notifications.
Does WhatsApp or Twilio have a limit amount of messages sent per second?
Is there any problem or additional cost if I send URL's in those messages?
I have a whatsapp business account.
Twilio developer evangelist here.
Twilio currently supports sending up to 25 messages per second through WhatsApp. If messages are sent at a rate higher than 25 MPS, Twilio maintains a queue. For very high outbound message volumes, messages can remain queued for up to 4 hours.
To achieve higher MPS, you can use Messaging Services. This allows you to distribute high volume across many WhatsApp senderes within the Messaging Service.
Related
In Firebase Cloud Messaging, Messaging report, count of received messages is more then sent. Why it is so ?
I have checked data in Biq Query and it differs with diagram. In Big Query data count of received messages is less then sent.
firebaser here
That data is unusual since normally send count should be greater than received. It’ll be challenging to pinpoint or even narrow down what could be the problem on a public forum without going into project-specific details. The issue can be in the FCM backend itself or just in the reporting metrics. I would recommend reaching out to Firebase support as they can offer personalized help.
Is there a way to use whatsapp cloud API to send mass messages as I don't want to use whatsapp business partner API.
If I am using a loop for sending multiple recipients then what about the message sending limit per second?
I am developing an app where I want to send notifications to multiple users from my backend server. These notifications will contain 4 different contents, three of them will go to 3 different users, but the forth one will go to more than 1000 users, the frequency of theses messages will be 3 to 7 times a week. Is it ok to send this amount of messages one by one using the Cloud Messaging api? Or should I group the messages before sending?
I thought about creating a topic in the Cloud Messaging, and subscribe the users to it and then send a message, but I don't if it is correct to keep subscribing/unsubscribing users just to send one message.
NOTE: I've never used any push notifications service before.
The Firebase Cloud Messaging infrastructure delivers billions of messages per day. The volume you're describing sounds well within reason for it.
Without knowing more about the use-case it's hard to say whether using a topic would be a better approach, so I recommend reading the documentation on topic messages to get a better understanding for it.
What are the restrictions for whatsapp Business API Groups.
Can I send messages all the time, or are these messages also restricted by the 24hr session time.
How many groups can I create, could I e.g. create 100 groups, 1 for every person attending some event?
Is there anywhere I can find the pricing for creating these groups?
From WhatsApp API FAQ
Can I send any message to any user at any time?
No.
If a user contacts an enterprise, the enterprise can respond with any type of message in the next 24 hours. This type of message is free.
But if the enterprise is contacting a user before the user sends a message or after more than 24 hours have passed, the enterprise can only send a message template. This is a paid notification.
Free-form text messages and media messages will not work outside this 24 hour window. They will result in a failure callback with error 470.
How many messages per second can I send?
The maximum tested outbound message rate is 20 messages per second.
How many messages can I send using google cloud messaging from my application per day to all registered devices.
Is there any limit per application per day ?
Thanks