CreateCallList
- __start_execution_time – when the call list processing starts every day, UTC+0 24-h format: HH:mm:ss
- __end_execution_time – when the call list processing stops every day, UTC+0 24-h format: HH:mm:ss
- __start_at – when the call list processing starts, UNIX timestamp. If not specified, the processing starts immediately after a method call
- __task_uuid – call list UUID. A string up to 40 characters, can contain latin letters, digits, hyphens (-) and colons (:). Unique within the call list
This method accepts CSV files with custom delimiters, such a commas (,), semicolons (;) and other. To specify a delimiter, pass it to the delimiter parameter.
IMPORTANT: the account’s balance should be equal or greater than 1 USD. If the balance is lower than 1 USD, the call list processing does not start, or it stops immediately if it is active.
Allowed roles: Owner, Admin, Developer, Call list manager.
Authentication
Voximplant Management API uses signed JWT tokens generated from your service-account private key. Pass the token in the Authorization header as a Bearer value:
Authorization: Bearer $VOXIMPLANT_TOKEN
See Authorization for ready-to-copy snippets in bash, Python, Node.js and Go that turn your credentials.json into a token.
Query parameters
Rule ID. It is specified in the Applications section of the Control Panel
Call list priority. The value is in the range of [0 ... 2^31] where zero is the highest priority
Number of attempts. Minimum is 1, maximum is 5
File name, up to 255 characters and cannot contain the '/' and '' symbols
Encoding file. The default value is UTF-8
Separator values. The default value is ';'
Location of the server where the scenario needs to be executed. Has higher priority than reference_ip. Request getServerLocations for possible values
Optional. Whether to prioritize first calling attempts or repeated ones. The possible values are: first_attempts, repeated_attempts. The default values is first_attempts.
Request
Send as the "body" part of the HTTP request or as multiform. The sending "file_content" via URL is at its own risk because the network devices tend to drop HTTP requests with large headers