API Blog

Communication and Data Quality APIs for real-time business solutions.

Archive for May, 2011


CDYNE PostBackURL for Phone Notify! and SMS Notify! APIs

Posted by: CDYNE  /  Tags: , , , , , , , , , , , , , , ,

CDYNE PostBackURL for Phone Notify! and SMS Notify! APIs

PostBackURLs allow Phone Notify! and SMS Notify! API customers to instantly know when an end user responds to a message or notification.  When a notification is sent out, CDYNE servers send a message back to the company’s designated PostBackURL noting the message has been sent.  When an end user responds, the results are also posted to the PostbackURL.

PostbackURL Assignment

A PostBackURL can be assigned to SMS Notify! and/or Phone Notify! request by using the advanced methods.  The advanced method for each service will have a property called StatusPostBackURL which is set with a link to the webpage created to handle a post back.  In addition, for incoming calls and text messages to a dedicated line that are not responses to previous messages, a StatusPostBackURL can be assigned directly to a customer’s DID (Phone number) allowing all end user generated traffic to go directly to the post back page.  This can be set up by contacting an account representative at 1-800-984-3710, sending an email inquiry or initiating a chat.

Using a PostBackURL with Phone Notify!

PostBackURLs can be very useful with the Phone Notify! API. It prevents the need to use the GetQueueIDStatus or GetMultipleQueueIDStatus methods. When using these methods, the customer’s server calls the methods multiple times as the customer would not know when the call has finished. With a PostBackURL in place, this allows the customer to have a webpage that will accept a POST from the Phone Notify! API when a call is placed, the call status has changed, the call is finished, or when a call is received (if using an Incoming DID).

When sending notifications, the PostBackURL can be set by using either the ~\StatusChangePostURL()~ script command at the beginning of the call script (especially when using NotifyPhoneBasic), or the StatusChangePostURL parameter in the NotifyPhoneAdvanced operation. When using an Incoming DID with the Phone Notify! API, a CDYNE account representative can assign a PostBackURL to that Incoming DID assigned to the customer’s account.

All available operations for the Phone Notify! API can be found here: http://ws.cdyne.com/NotifyWS/PhoneNotify.asmx, and advanced scripting commands can be found here: http://wiki.cdyne.com/index.php/Phone_Notify!_TextToSay_Advanced_Commands

Using a PostBackURL with SMS Notify!

With SMS Notify! There are several advantages to setting a StatusPostBackURL.  When a user responds to a message, CDYNE will immediately notify the SMS Notify! API customer via a post to the StatusPostBackURL. This eliminates the need for the customer to constantly query CDYNE servers for responses.

SMS Notify! API customers will receive a sent post with a PostBackUrl set in the request. The sent Post simply states the status of the SMS message at that time, and whether or not there were any minor errors in the request.  When this request is properly formatted, then the SMS message will be queued in the CDYNE system awaiting processing by the carrier.

If the recipient responds after the message has been sent, CDYNE will post the response post as well. The response post contains the recipient’s message and can be handled however your business model demands (i.e. storing the information in a database, or responding with another message).

The StatusPostBackURL can also be used with a dedicated line. A CDYNE representative can assign a customer’s designated StatusPostBackURL to their DID. Then, any incoming traffic to that number will result in a post to the designated StatusPostBackURL.  This is the preferred way to accommodate business models that want to make use of mobile originated messages.

There are two methods in SMS Notify! that makes use of a StatusPostBackUrl: http://sms2.cdyne.com/sms.svc/help/operations/AdvancedSMSsendhttp://sms2.cdyne.com/sms.svc/help/operations/SimpleSMSsendWithPostback.

Say It in Spanish, Canadian French, and German: CDYNE Phone Notify! API Features Three New Text-To-Speech Voices

Posted by: CDYNE  /  Tags: , , , , , , , , , , , , , , , ,

Spanish-Text-to-speech

CDYNE has upgraded its existing text-to-speech (TTS) voices, as well as added three new voices to the text-to-speech engine. With the addition of TTS voices Miguel, Jean-Pierre, and Matthias, your business can add scalable, multilingual, and customizable voice calls to your application. All voices have an 8kHz sampling rate. This is best suited to telephony applications because it eliminates the overhead that is incurred when using voices of a higher sampling rate.

New voices details:

  • Miguel (Americas Spanish), Male, Age 30 –  sample
  • Jean-Pierre (Canadian French) , Male, Age 30 - sample
  • Matthias (German) , Male, Age 30 – sample

All voices may be found here.

CDYNE’s text-to-speech engine converts raw text to written-out words, and then assigns phonetic transcriptions to those words. Text-to-speech can also be combined with recorded .wav files to create relevant call scripts according to your phone messaging web service needs. Call 704-323-7777 to listen to a sample recorded file and text-to-speech example.

Request a trial key to test Phone Notify! API for free by calling 1-800-984-3710, inquire or initiate a chat.

Text Messaging with Shared and Dedicated Long Numbers Using CDYNE SMS Notify! API

Posted by: CDYNE  /  Tags: , , , , , , ,

CDYNE SMS Notify! API

CDYNE SMS Notify! API is a versatile Web Service that allows businesses to send 2-way text messages worldwide through an SMS gateway using shared and/or dedicated long numbers. A long number (i.e. 757-544-9510) is a 10-digit phone number, and is an alternative method to short codes for sending outbound and receiving inbound SMS text messages. Customers using CDYNE SMS Notify! API can connect to a bank of shared long numbers, order dedicated long numbers (DIDs), or use a combination of both to support their business needs. Here is a quick overview of each option:

Shared Long Numbers

By using the SimpleSMS or AdvancedSMS request, users can pass their license key, phone number, and text message to CDYNE SMS Notify! API which will send the message(s) through a bank of randomly generated long numbers.  Text messages sent out this way will come from different phone numbers.

Dedicated Long Numbers

A significant feature of SMS Notify! API is the option for customers to purchase exclusively assigned long numbers, or DIDs. They allow inbound messaging for companies requiring Mobile Originated (MO) messages from customers or subscribers.

Customers may request a randomly generated DID, or specify the area code of the phone number.  Customers may purchase a single DID to be assigned to the license key or multiple DIDs to be assigned to a single license key.  Once the DID is issued, CDYNE assigns it to the customer’s license key which may be used to send text messages from the dedicated number(s). 

Combining Shared and Dedicated Long Numbers

In some cases, businesses may need to use a combination of both methods to send and receive text messages. To do this, users can use two separate SMS Notify! API license keys. It’s simple to generate an additional SMS Notify! API license key. And the best part is that it is free. Let’s use an example to illustrate.

Customer ABC creates license key xxx11yyy-1234-1a2b-3ca4-xxxe77e91yyy and assigns the key alias “Shared.” The customer can add a secondary key and assign with the alias, “DID 4723.” Customer ABC contacts CDYNE to order a DID. CDYNE staff place the order and assign the DID to license key “DID 4723.” With those steps complete, Customer ABC can program the license key called “Shared” to send out text messages on the bank of shared long numbers, as well as program the license key “DID 4723” to send and/or receive text messages from the dedicated phone number.

Test SMS Notify! API for free by requesting a trial license key by calling 1-800-984-3710, inquire or initiate a chat.