Push API Must Read Instructions

Read it carefully to avoid common mistakes

Broadcast API – Must Read Instructions (Phone Automation)

  1. This API allows you to send message with text , text + image , text + video, pdf, audio, document. Through a single API Call you can send Bulk or Dynamic Whatsapp Personal, Business or SMS’s.

  2. Sending one message takes 10 seconds , please consider this limitation while sending messages. i.e in a minute you can send only 6 messages. You have the option to change the delay between each message from the Picky Assist Bridge Android Application, by default it is set to 10 seconds and its recommended delay,

  3. If you would like to send 500 messages either static or dynamic in one go we highly recommend to pass the information in “data” variable in the JSON API, dont call the API 500 times for sending 500 messages at once or create any loops which will slow down your mobile phone.

  4. If you want to just give text response to an incoming messages then we highly recommend to give your reply message as JSON response to the Webhook request as its much faster than Broadcaster API.

  5. If you send messages very fastly and continuously to unknown contacts then there are high chances that your number may get blocked / banned by Whatsapp / Network Provider , we highly recommend to use this API for contacting customers who are already messaged or known to you or your business. Also encourage your customers to reply back or save your whatsapp number in their phone contacts.

  6. Use the priority tag only for sending priority messages since we process the queue based on this value , for an example if the messages dont need to be delivered instantly then we highly recommend to use low priority so that you can deliver a priority message instantly even if there is a queue.

  7. The media url should be available/accessible publicly and we recommend to keep the media size optimised for faster processing of messages and in order to process the media files fastly we download and save media files into your android phone then we create a hash based on the media url submitted by you , when you pass the same media URL again through API we look up whether the media is available in your phone or not , if the media is available in the phone we pick the media and send else we download the media again and send. So even if you change the media at your end (web server) the changes will not reflect so we recommend to pass a unique URL for each unique media rather than updating / changing the media from your backend (web server).

  8. To receive incoming messages / user replies in your server please configure webhooks from Settings -> Webhooks

  9. If you would like to send more concurrent messages in a minute or scale up further then please create more projects and share the load programmatically across different projects.

  10. If your phone is loaded with dual SIM card then SMS will go only from the default SIM where SMS is configured.