Voice
Quick Bulk Voice Call
The difference between Quick Bulk Voice Call and Quick Bulk SMS is the content of message. Here instead of using text as the message, you are going to use voice that you have recorded earlier in any format.
<strong>HTTP Request</strong>
POST https://api.mnotify.com/api/voice/quick
<p class="alert-danger"><i class="las la-info-circle" style="font-size:24px"></i>When you use voice file, do NOT use voice id and and also do NOT use voice file when you are using voice id</p>
<p class="alert-primary"><i class="las la-info-circle" style="font-size:24px"></i>_id is the id of the voice call sent. You can store this id somewhere to check the delivery status of your message. This id is also called campaign id voice_id is the id of the voice file you just used. You don't need to upload the same voice file when you want to place bulk voice call again using that voice file.</p>
<br>
<h3>Schedule Quick Bulk Voice Call</h3>
When scheduling quick bulk voice call, you must set is_schedule to true and include the date and time in schedule_date payload in the format YYYY-MM-DD hh:mm.When scheduling quick bulk voice call, you must set is_schedule to true and include the date and time in schedule_date payload in the format YYYY-MM-DD hh:mm.post/voice/quick
Path parameters
keystring required
Your enabled api key
campaignstring required
The title of your bulk voice call campaign
Array of phone numbers eg. ['0241234567', '0201234567']
{"stackTrail":"paths:/voice/quick:post:parameters:3:schema","oasType":"schema","type":"unknown"}
Your voice file in any format eg. mp3,wav etc
voice_idstring required
Your voice id when you already have a voice used before
is_scheduleboolean
Schedule flag. True means schedule message
{"stackTrail":"paths:/voice/quick:post:parameters:6:schema","oasType":"schema","type":"unknown"}
date and time in YYYY-MM-DD hh:mm if is_schedule is true
Response
Success
Changes
No recorded changes to this endpoint across all 1 revision of this API.