• Introduction
• Developer Guide Map
• Integration Basics

Introduction

• DOTS Telephone Verification (referred to as “Telephone Verification” or “TV”) is a publicly available XML web service with several methods to verify a telephone number. The verification options range from looking at the phone number’s exchange information to dialing the phone number
• in real time.
• Telephone Verification is accessible over three protocols: HTTP GET, HTTP POST, and SOAP over HTTP POST. Most programming languages
• have built-in classes to access web services over SOAP, but you may access the service via any of these three methods.

Developer Guide Map

• Operations
  • This section lists the DOTS Telephone Verification operations and goes into the details behind the inputs and outputs.
    • Operations:
      • PlaceCall (Recommended Operation)
      • SendSMS
      • GetPhoneInfo
      • GetExchangeInfo
• Notes
  • This section shows additional supporting data tables that are associated to the DOTS Telephone Verification operations
• Errors
  • Similar to the Notes section, this section reflects details on the error outputs that can happen with the service
• Code Snippets and Sample Code
  • Here you’ll find code snippets for various programming languages and frameworks along with links to our sample code page on the web site.
• Try The API

Integration Basics

• Integrating Telephone Verification into your application should be easy and straightforward. If you are using a common platform, such as asp, vb, C# .NET, PHP and others, Service Objects may already have sample code built that you can use:
• https://www.serviceobjects.com/developers/sample-code/

• However, if you are using a common platform that does not already have sample code, you can ask Service Objects to build an example for you. Email support@serviceobjects.com for more details.
  
• Web Service Structure
• Web services provide a standard interface to encapsulate tricky business logic. They allow simple integration of applications via the web.
• Service Objects has followed web services best practices and come up with some of its own standards to ensure that its web services are as easy to integrate and as accessible as possible.
• The host path, or physical location of the web service is here:
• https://trial.serviceobjects.com/rest/tv/api.svc
• A test page for the web service can be found here:
• https://trial.serviceobjects.com/rest/tv/
• The location of the WSDL, or Web Service Definition Language document, is here
• (This is also accessible via the “Service Definition” link.):

• https://trial.serviceobjects.com/tv/TelephoneVerification.asmx?WSD
•  

The WSDL is and XML document that defines the the interaction web service, meaning its inputs, outputs, operations, and the like. Most likely, you will have another tool read this WSDL and make the operations available to you in your application via some type of proxy class. Whenever your utilities or IDE asks for a WSDL path, you can provide this one. Every web service has operations that it offers to
subscribers. These operations, also called methods, contain different functionality and return different outputs.