Import API
Use the Import API to import customer contact information for an outbound campaign. You can import up to 10,000 records in one create request.
Note |
|
URL
https://<server>/unifiedconfig/config/campaign/<id>/importNote | You must specify the ID for a campaign that was created using the Outbound Campaign API. If you specify the ID for a campaign created using the Outbound Option Campaign tool, the request returns CceDBDataNotFoundException. |
Operations
-
create: Imports customer contacts for a specific campaign.
-
delete: Deletes the imported contacts for a specific campaign.
NoteThe delete operation deletes all imported contacts for the campaign. You cannot delete an individual record.
-
get (template): Returns a sample CSV template for contacts, which is provided by the API, using the URL https://<server>/unifiedconfig/config/campaign/import/template. The response contains the CSV template as a file attachment.
-
get: Retrieves the details of a single import record using the URL https://<server>/unifiedconfig/config/campaign/<campaignId>/import/<id>. The <id> is the ID of the imported contact.
-
get (csv file): Returns a CSV file for the contacts of the campaign, which is provided by the API, using the URL https://<server>/unifiedconfig/config/campaign/<campaignId>/import with header as "Accept" and value as "text/csv". The response contains the Contacts.csv as a file attachment.
-
get (csv file): Returns a CSV file for the contacts of the campaign, which is provided by the API, using the URL https://<server>/unifiedconfig/config/campaign/<campaignId>/import/csv. The response contains the Contacts.csv as a file attachment. In this operation, you do not need to send "Accept" header.
-
list: Retrieves a list of all imported contacts for the campaign.
-
Query parameters
-
Summary list: See list.
-
-
Parameters
Response Parameters for get:
-
accountNumber: The customer's account number.
-
callsMade: The number of calls made.
-
callStatus: The call status of the last call placed for this record. Possible values include the following:
-
active (A)
-
callbackRequested (B)
-
closed (C)
-
agentRejected (J)
-
maxAttemptsReached (M)
-
pending (P)
-
retry (R)
-
personalCallbackRequested (S)
-
unknown (U)
For more information about these values, see the CallStatusZone Values section of the Outbound Option Guide for Unified Contact Center Enterprise at https://www.cisco.com/c/en/us/support/customer-collaboration/unified-contact-center-enterprise/products-user-guide-list.html.
-
-
callResultOverall: The call result from the last call placed for this record.
-
firstName: The customer's first name.
-
lastName: The customer's last name.
-
importDate: The date and time that the record was imported.
-
phone01 through phone10: A collection of information about the customer's phones. Each phone contains the following parameters:
-
number: The phone number.
-
callResult: The call result from the last call placed for this phone number.
For more information about possible callResult values, see the CallResult Codes and Values section of the Outbound Option Guide for Unified Contact Center Enterprise at https://www.cisco.com/c/en/us/support/customer-collaboration/unified-contact-center-enterprise/products-user-guide-list.html.
-
dstObserved: Whether DST is observed for this phone's location. True or false.
-
gmtOffset: The number of minutes that the customer's time zone is offset from GMT. When you create import records, you can optionally provide a TimeZoneBias. The TimeZoneBias parameter represents the way information about time zones is stored in the Windows registry. You can use the following formula to convert TimeZoneBias to gmtOffset:
-
Parameters for create:
-
fileContent: Required. Comma-separated or pipe-separated list of data embedded within a CDATA section.
-
overwriteData: True or false. If set to true, the existing import data in the database is overwritten by the new import data. If set to false, the new import data is appended to the existing data. Default is false.
NoteYou cannot modify or remove existing fields or append a new field to existing data.
-
delimiter: Comma (,) or pipe (|). Default is comma (,).
-
header fields: The following header fields are allowed:
-
AccountNumber: Can contain any characters, including internationalized characters, except the delimiter specified in the input XML. Maximum length of 30 bytes.
-
FirstName: Can contain any characters, including internationalized characters, except the delimiter specified in the input XML. Maximum length of 50 characters.
-
LastName: Can contain any characters, including internationalized characters, except the delimiter specified in the input XML. Maximum length of 50 characters.
-
Phone01 through Phone10: Can contain digits 0-9, pound sign (#), and asterisk (*). Maximum length of 20 bytes. At least one Phone field is required.
-
TimeZoneBias: Specifies the offset of the customer's time zone from UTC in minutes. Integer. Range is from –780 to 720 (–13 to 12 hours from UTC).
-
DstObserved: Specifies whether DST is observed for the customer's location. True or false. Default is false.
NoteIf the TimeZoneBias parameter is provided but the DstObserved parameter is not, DstObserved is set to false. If the DstObserved parameter is provided but not TimeZoneBias, a validation error is returned.
If TimeZoneBias is not provided, time zone and Daylight Saving Time information is assigned by matching phone numbers to region prefix strings. If a phone number for a contact does not match a configured region prefix, the default time zone for the campaign is used.
If a customer record contains multiple phone numbers, the value for TimeZoneBias and DstObserved are applied to all of that customer's phone numbers.
You can use the Time Zone API to look up the values for TimeZoneBias and DstObserved for the target time zone. For more information, see Time Zone API.
-
Search and Sort
The following table shows the parameters that are searched and the parameters that are sortable.
Search parameters | Sort parameters |
---|---|
|
|