---
title: "Quick Bulk Voice Call"
method: POST
path: "/voice/quick"
tags: ["Voice"]
---

# Quick Bulk Voice Call

`POST /voice/quick`

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.

## Path parameters

- `key` string, required
- `campaign` string, required
- `recipient` unknown[], required
  - unknown
- `file` unknown, required
- `voice_id` string, required
- `is_schedule` boolean
- `schedule_date` unknown

## Response `200`

Success

- CampaignBulkVoice
  - `status` string
  - `code` string
  - `message` string
  - `summary` object

---

[API](https://skmtc.dev/mnotify/apis/bms-documentation.md) · [All operations](https://skmtc.dev/mnotify/apis/bms-documentation/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/mnotify/bms-documentation/revisions/c06855f2ed03/schema)