Comment on page
Dialer
Send a pre-recorded message to a user's phone number and receive a result that will let you know if the message was delivered.
This service includes two POST request:
- Initial request - defines which message to send and to what phone number. This request will also return a template with a unique token that should be submitted in the status request.
- Status Request - a request with the template and token from the initial request to retrieve the status of the call.
Provide your Veratad representative with the audio file you want to be delivered. You can have as many audio files as necessary. Once you have provided the audio file then Veratad will provide you with that files unique name which you will send as part of the initial request in the
message attribute. Please see the section below called "What types of audio files are acceptable" for a full list of file types.
As part of this process you are also validating the number the user provided since the service will not send to invalid phone lines.
post
https://production.idresponse.com
/process/comprehensive/gateway
PhoneMatch5.0.Dialer (initial request)
{
"user": "[email protected]",
"pass": "PASSWORD",
"service": "PhoneMatch5.0.Dialer",
"reference": "12345",
"options": {
"outofband": {
"message": "test.message",
"do_not_send_to_types": ["voip", "mobile", "landline"]
}
},
"target": {
"phone": "2015106000"
}
}
The following are all values that will be returned in the result object of the response.
Action | Detail | Description |
FAIL | SUPPRESSED SENDING CODE | The phone line type was detected as one of the line types passed in the options object in the do_not_send_to_types array |
FAIL | FAILED TO SEND TO NUMBER | An issue occurred during password delivery and it never reached the user |
FAIL | DATA CHECK FAILED | The phone number is invalid and the code could not be sent |
PENDING | TRANSACTION REQUIRES FURTHER ATTENTION | The line type is not in the do_not_send_to_types array, the number is valid and the message was sent to the user. You may now send a subsequent request to get the status. |
post
https://production.idresponse.com
/process/continue
PhoneMatch5.0.Dialer (message status request)
{
"dialer": {
"return": "status"
},
"token": "ssskwryi5u5t222kd3sqjey4axsnonl8"
}
Action | Detail | Description |
FAIL | MESSAGE COULD NOT BE DELIVERED | Something went wrong and the message was never delivered to the customer. |
PENDING | MORE INFORMATION IS REQUIRED | The call is still in progress. Take the template returned and submit again. |
PASS | ALL CHECKS PASSED | The number is valid, the line type was not found in the do_not_send_to_types array, the message was successfully sent and was delivered. |
PhoneMatch+Dialer will process with the default base ruleset:
The base ruleset will return a PASS when:
- The phone number is valid
- The phone line type is not found in the
do_not_send_to_typesarray - The message was sent successfully
The base ruleset will return a PENDING when:
- The phone number is valid
- The phone line type is not found in the
do_not_send_to_typesarray - The message was sent
- The transaction is waiting for you to check the status
The base ruleset will return a FAIL when:
- The phone number is not valid
- The phone line type is found in the
do_not_send_to_typesarray - The message was not sent successfully
You must provide Veratad with the audio file that you want delivered. Once you have provided this file Veratad will supply you with the files name in the system for you to populate the
message attribute in your initial request. Here are all of the acceptable file types:
MIME type | Description |
audio/mpeg | mpeg layer 3 audio |
audio/wav | wav format audio |
audio/wave | wav format audio |
audio/x-wav | wav format audio |
audio/aiff | audio interchange file format |
audio/x-aifc | audio interchange file format |
audio/x-aiff | audio interchange file format |
audio/x-gsm | GSM audio format |
audio/gsm | GSM audio format |
audio/ulaw | u-law audio format |
Last modified 3yr ago