DEV Outbound APIs

- NEW! - Interactive API docs, now live!

Visit api-docs.plumvoice.com to read Plum API documentation, build and test requests in our interactive API sandbox, review the responses, and share it all with your team.

Outbound API Methods

Queue a Single Call with the queuecall web service

This default campaign and the calls within it are visible in and controlled from your campaign management interface after you login with your login name and PIN.‌ If you do not already have a PIN for outbound calling, contact Plum's Account Management team.

If you plan to queue more than one call at a time, use the Queue Multiple Calls API Method. Looping the Single Call API for individual calls can cause DDoS, which will result in all calls failing.

Queue A Single Call

POST http://outbound.plumvoice.com/webservice/queuecall.php‌

The queuecall API method allows users to initiate a call to a specific phone number. Initiating an outbound call in this manner places the call into the default calling campaign for your account.

Request Body

<?xml version="1.0"?>
<queuecall status="queued" call_id="112850593">
    <login>user</login>
    <pin>98765432</pin>
    <phone_number>+1234567890;ani=8001234567</phone_number>
    <start_url>http://charles.plumgroup.com/~schan/src/charles/vxml/start.php</start_url>
</queuecall>

See the Outbound API parameter notes for additional information on these single call API parameters.

Queue Multiple Calls with the queuecalls web service

The campaign manager interface allows users to assign campaigns a unique name and to manage various aspects of the campaign. Use your login name and PIN to access the campaign manager.‌ If you do not already have a PIN for outbound calling, contact Plum's Account Management team.

Queue Multiple Calls

POST http://outbound.plumvoice.com/webservice/queuecalls.php‌

The queuecalls API method allows users to initiate calls to any number of callers listed in an uploaded text file. Initiating a group of outbound calls in this manner creates a calling campaign.

Headers

Request Body

<?xml version="1.0"?>
<queuecalls status="success">
    <login>user</login>
    <pin>98765432</pin>
    <campaign_name>SunnyCamp</campaign_name>
    <start_url>http://charles.plumgroup.com/~schan/src/charles/vxml/start.php</start_url>
    <phone_list>
        <call call_id="112897970">
            <phone_number>tel:+19492222222;ani=8009957586</phone_number>
        </call>
        <call call_id="112897971">
            <phone_number>tel:+19492222223;ani=8009957586</phone_number>
        </call>
    </phone_list>
</queuecalls>

You must POST with multipart/form-data encoding in order for the queuecalls webservice to properly receive and process the uploaded file .‌

All settings are applied to all calls in the campaign. However, message_reference and call_parameters (see below) are set on a per-call basis and are specified in the uploaded text file with each phone number.‌

Required Settings

Calls are listed in the phone number list file on comma-delimited lines where the first field is the phone number and the second and third fields contain a message_reference string and call_parameters string, respectively, for the call as described here. The second and third fields are optional.‌

See the Outbound API parameter notes for additional information on these multi-call API parameters.

Last updated