• Error Types
  • Error type 1: Authorization
  • Error type 2: User Input
  • Error type 3: Service Objects Fatal
  • Error type 4: Domain Specific

Generally, an error is anything that happens during execution of DOTS Telephone Verification that causes the service to fail. The source of these errors may be user input, license key transaction limits, timeouts, and unexpected circumstances. Applications should expect and handle any and all errors appropriately. Occasionally, new error types or descriptions may be introduced to the web service as new features and data sources are implemented. Description strings may change slightly, so use the description code to determine which error has occurred. Errors are organized into types, listed in the table below.

There are four error types described below.

Error Types

Error type 1: Authorization

The Error object appears under the main return object. Below is an example of the error returned when the PlaceCall operation is accessed without a valid license key

<TelephoneInfo>
<Error>
<Type>Authorization</Type>
<TypeCode>1</TypeCode>
<Desc>Please provide a valid license key for this web service.</Desc>
<DescCode>1</DescCode>
</Error>
</TelephoneInfo>

Error type 2: User Input

User Input errors are caused when a user inputs an invalid value or fails to provide a certain input field altogether. If a developer creates a request and mistypes a parameter name, it will probably cause a User Input Error.

*Deprecated DescCode that are no longer used.

Error type 3: Service Objects Fatal

The Desc will always be the same and the DescCode has no meaning. This is standard to all Generation 2 DOTS Web Services. This is a rare error that signals either a bug in the DOTS Address Validation 2 service, or a Network/Connectivity issue.

Error type 4: Domain Specific

Domain specific errors represent the common errors seen in Service Objects services.