Introduction
- DOTS GeoPhone (referred to as “GeoPhone” or “GP”) is a publicly available XML web service that provides reverse phone lookup information about a US (or sometimes Canadian) phone number. The service provides name, address, city and state, along with carrier exchange information. GeoPhone can provide instant reverse-phone lookup verification to websites or data enhancement to contact lists. However, the output from GP must be considered carefully before the existence or non-existence of a given phone number is decided.
Developer Guide Map
- Operations
- This section lists the DOTS GeoPhone operations and goes into the details behind the inputs and outputs.
- Operations:
- GetPhoneInfo_V2 (Recommended Operation)
- GetPhoneInfoLastFirst
- GetExchangeInfo (Deprecated)
- GetContactInfo (Deprecated)
- GetPhoneInfo (Deprecated)
- Operations:
- This section lists the DOTS GeoPhone operations and goes into the details behind the inputs and outputs.
- Errors
- 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
- This is where you’ll go to take the API for a spin. There you can test our recommended operation GetPhoneInfo_V2 (Recommended Operation).
- Service Reference
- 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.
- Frequently Asked Questions
- This is a list of some of the questions we hear more often that you can reference and get answers on right away.
Integration Basics
- Integrating GeoPhone into your application should be easy and straightforward. If you are using a common platform, 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 you an example. Email support@serviceobjects.com for more details.
- Web Service Structure:
- Web services are methods that integrate with other applications via the web, and encapsulate tricky business logic. Web services are too large of a topic to cover in this document, but Service Objects has developed its web services to be as easy to integrate and as accessible as possible. GeoPhone is a public XML web service that supports SOAP, POST and GET operations. Note that SOAP is done via POST, only with special XML markup in the post-body.
- The host path, or physical location of the web service is here:
https://trial.serviceobjects.com/gp/
- 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/gp/soap.svc?wsdl
- This WSDL is the definition of the 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. Whenever your utilities or IDE asks for a WSDL path to GeoPhone, you can provide this one.
- Every web service has operations that it offers to subscribers – methods that do different work and return different output. Examining the link above, you will notice several of these operations available, which are described in detail later on.