Is there away around creating a list with ListCreate

I'm attempting to automate the call process in our organization using the EL API's. However, it looks like uploading a list is necessary. Is this the case or is there a way to submit a voice request without having to store a list? Currently that process is done through the portal but can probably be automated but it would be better to even remove that step and just send the voice request.

Find more posts tagged with

Comments

skamens

You absolutely do not need to store a list - the recipient list can be included with the JobSubmit request.

Click here for a sample voice job submission that includes the recipients via a CSV in the request.

Apandit

So what you're saying is that if I wanted to for each request I could include the list rather than create one first? So I can send one message with a list or many with a list right?

It looks like the sample is simple sending the voice request. I can't tell but is the WAV being sent across the wire or does it already exist on the server and only being reference by name? Currently we don't plan to send the WAV's over the wire, yet.

My scenario is mostly like this:

1. Currently someone uploads a list to the portal.
2. The WAV's (voice recordings) are also uploaded (my guess is these are uploaded first).
3. CL calls based on the voice and information in the list.

What I'm trying to do is avoid the list upload in favor or sending the request using the EL API's.

skamens

In general, the components of a job are not passed by reference - they are usually included with the job somehow.

For voice deliveries, there are some exceptions. If a TTS template or a voice script are being used, those get stored on the system ahead of time and referenced by the job. But any wav files that are needed would need to be uploaded. Having said that, it is possible to have those files on a web server or our internal customer file store, and then to refer to them from your job submit request.

But however the job payload gets referenced, you can definitely send the list of (one or more) recipients in the JobSubmit request without having to upload the list as a separate step.

Apandit

Is there an example more in line with this use case?