Informizely customer feedback surveys
By using the Aculab site, you agree with our use of cookies.

Web Service Errors

ErrorDescription
0001A mandatory parameter has not been specified. The missing parameter will be mentioned in the error string.
0002The 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.
0003Multiple versions of the same named parameter have been passed to the web service, where only one is required.
0004The parameter type is numeric, but with a value of zero. This is not allowed.
0005No regulation address has been specified when attempting to buy a number, but this country requires one to be associated with the purchased numbers.
0006The 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.
0007A 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.
0008The server doesn't know the country with the specified DID type.
0009The region is unknown to the server.
0010The state is unknown to the server.
0011You'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.
0012The supplied regulation address does not exist under your account.
0013Data within this call needs to be conducted over HTTPS as it contains personal information.
0014Your request needs to send a method type of either GET or POST.
0015The 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.
0016This operation requires a filename to be passed, which is missing.
0017The filename supplied can't be found on the server.
0018The server had a problem when accessing storage.
0019The POST request to the server is empty.
0020No content length has been supplied to the server.
0022Basic HTTP authentication of your request failed because the Username or 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.
0023A mandatory parameter has been specified, but its contents is empty.
0024A parameter has been specified as a list, but one or more of its elements are empty.
0025The 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.
0026There must be at least a minute gap between conference manipulation requests.
0027The API service to use is unknown to the server.
0028States are only used by geographic numbers in limited countries. They are not required in national or toll-free numbers.
0100You're using a Developer account, but need a Production or Premium account to perform this operation.
0101The account has insufficient funds to perform the operation. The error message will tell you how much credit is required to allow the operation.
0102The operation cannot be performed because it is forbidden. You've supplied an unknown based_on parameter.
0103The username supplied is invalid.
0104The application instance ID supplied does not exist.
0105A request to interrupt a REST application has been received, but the application has already completed.
0200There 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.
0201did_type must be one of geographic, national or tollfree.
0202You 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.
0203Calls from phones of the supplied type to toll free numbers with the supplied country and region (prefix) are not allowed.
0300The telephone number to delete does not belong to your account, so it cannot be deleted.
0301The telephone number either does not exist, or does not belong to your account.
0401The filename supplied is illegal on the Aculab Cloud. Only ASCII values greater than 32, along with slash, dash, @, underscore, and colon are allowed.
0402The 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.
0403The from parameter is missing.
0404The to parameter is missing.
0405The 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.
0406A valid MEDIA filetype has been supplied. However, MEDIA filetypes cannot operate with the requested function.
0407A valid REST filetype has been supplied. However, REST filetypes cannot operate with the requested function.
0408The supplied filetype must be one of the types given in the error message.
0500The supplied report type is unsupported. Valid report types can be one of the following: adr, cdr, err.
0501The report file type is unsupported. Valid report file types are: csv and json.
0503When generating a full report, a json report file type must be requested.
0504The 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.
0505The supplied from date and time must come before the to date and time.
0506You've requested a report convering more days that the two month maximum allowed.
0507You've already requested an identical report, which is still being generated.
0600The supplied number of participants is invalid. It needs to be between a range as specified by the web service, inclusive.
0601The 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.
0602The supplied conference duration is invalid. It must be in minutes and in the range specified in the error text.
0603A conference with this name is already reserved.
0604The reservation_token is not valid.
0605This conference can't be modified, as it's already been cancelled.
0606The request would increase the total conference duration to above 480 minutes.
0607This conference has already finished.
0608This conference is due to start in less that five minutes, so it's too late to cancel it.
0609The conference has already started, and you can't cancel a conference while it's running.
0610This conference is due to finish in less than five minutes, so it's too late to extend its duration.
0611The conference start time must be after the current time.
0612You've tried to reserve a conference with more participants than are allowed on your account.
0613No conference of that name is currently known to the system.
0614No participant of that name is currently known to the system.
0615The conference is not currently in the running state.
0616Both the conference_name and reservation_token parameters have been supplied rather than just one or the other.
0617At least one of the participant options must be specified
0700You've supplied a "from" number which is not one you've purchased on your Aculab Cloud account, so the message could not be sent.
0701The 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.
0702Delivery 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.
0703The content can't be encoded into a form we can send to the carrier, so your message could not be sent.
0704The content is too long for us to split into individual messages we can send to the carrier, so your message could not be sent.
0705The 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.
0706The type is unhandled. We support sms only, so your message could not be sent. Please try again using type sms.
0707The 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.
0708Messages 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.
0709Either "to" or "from" is missing. One or the other parameter must be supplied
0710Either the 'to' or "from" field must be presented. You cannot present both.
0711This would exceed the maximum number of messages for this phone number in the message queue, so the message could not be sent.
0712You'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.
0713Your account must be configured to use flash SMS. Please contact support.
0714Your account must be configured to use alphanumeric sender IDs. Please contact support.
1001An internal error has occured. The web service is still available, but this may indicate a fault with our server.
1002The web service has been unable to communicate with it's backend server, meaning the operation cannot continue. This is usually a temporary error message.
1003You are using this web service at too high a rate, meaning the operation you requested cannot continue. Please use it at a lower rate.
1004The web service has been unable to communicate with it's backend server, meaning the operation cannot continue. This is usually a temporary error message.
2001Your UAS connected to the Cloud, but failed to authenticate successfully. This is almost certainly because the Cloud, username and password supplied to the UAS don't match those of your Cloud account on the web site. Note that this can occur if you change your Cloud account password on the site - in that case, you need to change your password on the UAS as well.
2002Your UAS connected to the Cloud and authenticated successfully, but subsequent handshaking failed.
2004The Cloud wanted to start one of your applications, found a UAS which had it loaded, but the application failed to start.
2005A REST application could not be started, due to invalid or missing data in either the service settings or application parameters.
2007An 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.
2008The 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
2011Your UAS connected with the Cloud and authenticated successfully, but subsequent handshaking failed due to a mismatch in its significant version number.
2013An incoming call to the DDI noted in the text was hung up due to there being no credit on the account.
2014A call with the DDI noted in the text was hung up due to there being no credit on the account.
2016One or more running applications were stopped due to there being no credit on the account.
2017One or more running applications were stopped due to the account being on administrative hold.
2018An incoming call to the DDI noted in the text was hung up due to the account being on administrative hold.
2019A call with the DDI noted in the text was hung up due to due to the account being on administrative hold.