This page lists the error codes that can be returned by the webservice, click the error code for more information and potential solutions to common issues
|A mandatory parameter has not been specified. The missing parameter will be mentioned in the error string.
|The parameter is malformed. This error will be produced if the string sent fails a sanity check of the data that is sent to the web service. For example, specifying a country with numbers will produce this error.
|Multiple versions of the same named parameter have been passed to the web service, where only one is required.
|The parameter type is numeric, but with a value of zero. This is not allowed.
|No regulation address has been specified when attempting to buy a number, but this country requires one to be associated with the purchased numbers.
|The named regulation address is not compatible with the country and region being used. There are three types of addresses that can be required: Local, National and Worldwide. A Local address means the regulation address supplied must be located in the same region and country as the number you're trying to purchase. National means any regulation address can be used, as long as it is located within the country the numbers are trying to be purchased from. Finally, Worldwide means any address in the world can be used for a regulation address.
|A boolean parameter must be specified as either 'True', 'T' or '1' for true, or 'False', 'F' or '0' for false. Sending anything else will result in this error message.
|The server doesn't know the country with the specified DID type.
|The region is unknown to the server.
|The state is unknown to the server.
|You've supplied a state, but numbers with the DID type and in the country supplied are not associated with states. Perhaps the country doesn't have states.
|The supplied regulation address does not exist under your account.
|Data within this call needs to be conducted over HTTPS as it contains personal information.
|The request method you have specified is not allowed.
|The Cloud ID given in the request was invalid, it must be in the form Region-Layer-Cloud. See https://www.aculab.com/cloud/guides/cloud-regions for more information.
|This operation requires a filename to be passed, which is missing.
|The filename supplied can't be found on the server.
|The server had a problem when accessing storage.
|The POST request to the server is empty.
|No content length has been supplied to the server.
|The request could not be decoded. This error occurs when either the request body does not match the specified content type and content encoding, or the query contains invalid characters.
|Basic HTTP authentication of your request failed because the Username or API Access Key/outbound service password you provided was incorrect. See https://www.aculab.com/cloud/other-apis/web-services/web-services-overview for information on how to set them, unless you're requesting service_start in which case see https://www.aculab.com/cloud/other-apis/web-services/starting-outbound-services instead.
|A mandatory parameter has been specified, but its contents is empty.
|A parameter has been specified as a list, but one or more of its elements are empty.
|The reference ID parameter is malformed. The ID consists of three parts, seperated by a dot. The first is hexidecimal, the other two purely decimal. Ensure that every ID you pass is one that was returned from the web services API. If you need to provide more than one, separate with a forward slash.
|There must be at least a minute gap between conference manipulation requests.
|The API service to use is unknown to the server.
|States are only used by geographic numbers in limited countries. They are not required in national or toll-free numbers.
|A parameter has been specified which is not recognised by this API.
|The parameters specified are incompatible with one another.
|The specified parameter is required to be unique, but the supplied value already exists in the system.
|The HTTP request did not contain a Content-Type header or contained a Content-Type header that was invalid.
|You're using a Developer account, but need a Production or Premium account to perform this operation.
|The account has insufficient funds to perform the operation. The error message will tell you how much credit is required to allow the operation.
|The operation cannot be performed because it is forbidden. You've supplied an unknown based_on parameter.
|The username supplied is invalid.
|The application instance ID supplied does not exist.
|A request to interrupt a REST application has been received, but the application has already completed.
|Your account has been deactivated and it is no longer possible to make any web service requests. If this message is a suprise to you, please contact support.
|Your account has not been enabled for access to VoiSentry. If you think this is incorrect, please contact support.
|There isn't sufficient stock of inbound numbers in the required area to complete this request. Consider purchasing stock in another areas. Alternatively, let us know, and we might be able to increase stocks.
|did_type must be one of geographic, national, tollfree or mobile.
|You can choose which phone types can call your toll-free number, the cost-per-minute depending on which options you pick. Your API call had no allowable types. At least one must be allowed.
|Calls from phones of the supplied type to toll free numbers with the supplied country and region (prefix) are not allowed.
|The telephone number to delete does not belong to your account, so it cannot be deleted.
|The telephone number either does not exist, or does not belong to your account.
|The telephone number has not been found in the whitelist for your account.
|The filename supplied is illegal on the Aculab Cloud. Either one or more characters were invalid, there was problem with the file extension or there was a problem with the file path.
|The format of the WAV or TIFF file you're uploading is not supported by Aculab Cloud. See https://www.aculab.com/cloud/guides/sending-and-receiving-faxes for more information about which WAV formats are supported, and https://www.aculab.com/cloud/guides/sending-and-receiving-faxes/supported-fax-formats for TIFF specifications.
|The from parameter is missing.
|The to parameter is missing.
|The token provided is either invalid, lapsed, or otherwise unidentified. Note that tokens returned by media_delete are stored for only four hours after delete completion.
|A valid MEDIA filetype has been supplied. However, MEDIA filetypes cannot operate with the requested function.
|A valid REST filetype has been supplied. However, REST filetypes cannot operate with the requested function.
|The supplied filetype must be one of the types given in the error message.
|The number of hours to live is greater than the maximum specified in the error message.
|The number of days to live is greater than the maximum specified in the error message.
|The number of minutes to live is greater than the maximum specified in the error message.
|The time to live specification is invalid. This should be in the format n[d|h|m], which n is the unit, and [d|h|m] specifies days, hours or minutes.
|You cannot specify a time to live for this filetype. Time to live can only be specified for MEDIA files.
|You cannot upload encrypted MSG_MEDIA files. You can only upload encrypted MEDIA files.
|The prefix paramater can not contain a / character.
|The supplied report type is unsupported. Valid report types are: 'adr', 'cdr', 'fdr', 'msg' and 'err'.
|The report file type is unsupported. Valid report file types are: csv and json.
|When generating a full report, a json report file type must be requested.
|The specified date and time are in the incorrect format. Format must be YYYY-MM-DD_hh:mm:ss, with the date and time in UTC.
|The supplied from date and time must come before the to date and time.
|You've requested a report convering more days that the two month maximum allowed.
|You've already requested an identical report, which is still being generated.
|The from date is too far in the past, data is only stored for 6 months, including the current month.
|You currently have the maximum number of reports in progress. You must wait for existing reports to complete before you can start more.
|Your report cannot be started at this time due to capacity restrictions on the cloud. In order to maintain quality of the cloud as a whole we limit the total number of active reports across the cloud.
|The supplied number of participants is invalid. It needs to be between a range as specified by the web service, inclusive.
|The start time supplied is invalid. Time must be UTC in the format YYYY-MM-DD-HH-MM, all integers. It must be at least five minutes away and not more than 24 hours away.
|The supplied conference duration is invalid. It must be in minutes and in the range specified in the error text.
|A conference with this name is already reserved.
|The reservation_token is not valid.
|This conference can't be modified, as it's already been cancelled.
|The request would increase the total conference duration to above 480 minutes.
|This conference has already finished.
|This conference is due to start in less that five minutes, so it's too late to cancel it.
|The conference has already started, and you can't cancel a conference while it's running.
|This conference is due to finish in less than five minutes, so it's too late to extend its duration.
|The conference start time must be after the current time.
|You've tried to reserve a conference with more participants than are allowed on your account.
|No conference of that name is currently known to the system.
|No participant of that name is currently known to the system.
|The conference is not currently in the running state.
|Both the conference_name and reservation_token parameters have been supplied rather than just one or the other.
|At least one of the participant options must be specified.
|You've supplied a "from" number which is not one you've purchased on your Aculab Cloud account, so the message could not be sent.
|The mobile phone with number "to" has previously sent an opt-out message to stop further messages from your "from" number. It's not since then sent an opt-in message, so your message could not be sent.
|Delivery reporting has been requested, but this is not supported to this "to" number by the carrier used to send messages from your "from" number, so your message could not be sent.
|The content can't be encoded into a form we can send to the carrier, so your message could not be sent.
|The content is too long for us to split into individual messages we can send to the carrier, so your message could not be sent.
|The content is too long for us to send as a single message to a non multipart capable carrier, so your message could not be sent.
|The type is unhandled, so your message could not be sent. Please check to documentation to see which types are supported.
|The status_method is unhandled. We support POST and GET only, so your message could not be sent. Please try again using an allowed status_method.
|Messages are not enabled on this "from" number, so your message could not be sent. To enable messages on this number, click Account, Purchases and ensure a green envelope is displayed for the number. If a red envelope is displayed, click to change to green. Note that, to send messages, this number must have been purchased from Aculab Cloud.
|Either "to" or "from" is missing. One or the other parameter must be supplied.
|Either the 'to' or "from" field must be presented. You cannot present both.
|This would exceed the maximum number of messages for this phone number in the message queue, so the message could not be sent.
|You've supplied a "to" number which is invalid or has a country code which Aculab Cloud cannot send to, so the message could not be sent.
|Your account must be configured to use flash SMS. Please contact support.
|Your account must be configured to use alphanumeric sender IDs. Please contact support.
|Your account must be configured to allow sending SMS to US telephone numbers.
|Messages of the type requested do not support using the named parameter.
|Messages of the type requested require the use of the named parameter.
|There was a problem with at least one message media file.
|US SMS requires a campaign registration ID recorded against all numbers used for sending A2P SMS messages.
|This 'from' number has a campaign registration ID, but the campaign registration has expired.
|SMS must contain visible characters.
|MMS must have media file attachments.
|SMS cannot have file attachments.
|The message type requested is not currently supported on this number.
|Your account must be configured to allow sending SMS.
|A token must provide permission for at least one usage, but none were specified.
|Developer accounts are limited to 1000 tokens per month for testing.
|Convert job not found. Token is invalid, lapsed, or otherwise or otherwise unidentified. Please note that file convert job status is stored for a limited time only. Please refer to the documentation for more details.
|Your trial account period has expired.
|Trial accounts are only able to purchase telephone numbers in the country where the account is registered.
|Trial accounts are only able to purchase geographic and mobile numbers in the country where the account is registed.
|Trial accounts are limited in the number of telephone numbers they can own and you have reached that limit.
|Trial accounts are limited in the number of concurrent outbound services they can run.
|An internal error has occured. The web service is still available, but this may indicate a fault with our server.
|The web service has been unable to communicate with it's backend server, meaning the operation cannot continue. This is usually a temporary error message.
|You are using this web service at too high a rate, meaning the operation you requested cannot continue. Please use it at a lower rate.
|The web service has been unable to communicate with it's backend server, meaning the operation cannot continue. This is usually a temporary error message.
|The web services are used at a too high a rate, meaning the operation you requested cannot continue. Please use it to finish processing.
|The account is using the web services at too high a rate, meaning the operation you requested cannot continue. Please use it at a lower rate.
|The outbound service is being used at a too high a rate, meaning the operation you requested cannot be handled. Please allow outstanding requests to finish processing.
|Unsupported or missing Content-Type header. Expected application/pdf.
|Could not find a PDF attached in the request body.
|Your UAS connected to the Cloud, but failed to authenticate successfully. This is almost certainly because the Cloud, username and API Access Key supplied to the UAS doesn't match those of your account. Note that this can occur if you generate a new API Access Key on the Cloud Console - in that case, you need to re-enter your credentials in the UAS.
|Your UAS connected to the Cloud and authenticated successfully, but subsequent handshaking failed.
|The Cloud wanted to start one of your applications, found a UAS which had it loaded, but the application failed to start.
|A REST application could not be started, due to invalid or missing data in either the service settings or application parameters.
|An incoming call to the DDI noted in the text was hung up because, while it matches one of your inbound services, there was no UAS available that could run the application used by that service.
|The UAS or its application with the Application Instance Id and Application Parameters noted in the text started but, on completion, returned the failure code noted. Results from -1 to -99 are created by the UAS system, and -100 below are user created. For system specific Python UAS errors, see https://cloud.aculab.com/documents/api/python/latest/adr.html#adr-info. For .NET UAS system specific errors, see https://cloud.aculab.com/documents/api/dotnet/latest/UASCSharpWritingApplications.html under Application Rules.
|The REST application with the Application Instance Id and Application Parameters noted in the text started but, on completion, returned the failure code noted. Results from -1 to -104 are reserved for the REST system, and -105 below are user created.
|Your UAS connected with the Cloud and authenticated successfully, but subsequent handshaking failed due to a mismatch in its significant version number.
|An incoming call to the DDI noted in the text was hung up due to there being no credit on the account.
|A call with the DDI noted in the text was hung up due to there being no credit on the account.
|One or more running applications were stopped due to there being no credit on the account.
|One or more running applications were stopped due to the account being on administrative hold.
|An incoming call to the DDI noted in the text was hung up due to the account being on administrative hold.
|A call with the DDI noted in the text was hung up due to due to the account being on administrative hold.