DOTS Phone Exchange 2 is an XML/JSON web service that provides information about telephone numbers. With DOTS Phone Exchange 2 users can verify telephone numbers, receive geographic location and carrier information of any phone number in the U.S., In addition, it also provides Local Number Portability data in the event the phone number has been ported between Carriers and LineType.
NOTE: The DOTS Phone Exchange 2 web service has recently been updated, and as such some of the older operations have been deprecated. If you are still currently using the older operations of the service, you can refer to the developer's guide below for information concerning integration, inputs and outputs for the deprecated operations.
If you are an existing client and are using the previous version of this service then please click on the following link.
This section lists the DOTS Phone Exchange 2 operations and goes into the details behind the inputs and outputs.
GetExchangeInfo (Recommended Operation)
This section shows additional supporting data tables that are associated to the DOTS Phone Exchange 2 operations.
Similar to the Codes, Notes, and Corrections section, this section reflects details on the error outputs that can happen with the service.
Here you'll find code snippets for various programming languages and frameworks along with links to our sample code page on the web site.
This is where you'll go to take the API for a spin. There you can test our recommended operation GetExchangeInfo.
In this section you'll find all the different endpoints supported by this service, input and output schema information as well as an opportunity to try the other endpoints as well.
This is a list of some of the questions we hear more often that you can reference and get answers on right away.
Integration of DOTS Phone Exchange 2 into user applications is generally a straightforward process. For common programming platforms, such as ASP, ASP.NET, ColdFusion, PHP, etc., Service Objects will likely have sample code available online:
If the code you seek is not available online, you can ask Service Objects to build a custom example for you. Email firstname.lastname@example.org 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:
The location of the WSDL, or Web Service Definition Language document, is here (This is also accessible via the "Service Definition" link on the web service page.):
SOAP is done via POST, only with special XML markup in the post-body
The WSDL is an XML document that defines 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. DOTS Phone Exchange 2 has one operation, it will be described in detail later in this document.
We want to hear from you! We're always looking to improve our developer guides.
Please email your suggestions to email@example.com.