Interface information

tyntec’s Global Number Verification (GNV) minimizes message loss and unsuccessful call attempts with real-time phone number verification, providing key information on your users’ phone numbers, such as subscriber status and roaming data.

Global Number Verification is available with the Asynchronous SOAP API.

SOAP is a protocol used for exchanging messages over a computer network. The messages that are sent do not rely on the underlying transport protocol, which is HTTP post in most cases (and in the specific case of the tyntec infrastructure).

The messages themselves are structured as XML documents and are defined in two parts:

  • SOAP standard
    The SOAP standard describes elements necessary for communication, such as the “SOAP Envelope” which encloses the actual content to be sent. This content is application-specific and is in this case defined by the WSDL file provided by tyntec. A simple XML parser can be used for extracting the data from the soap response.

To implement and use Global Number Verification, you should have certain resources:

  • The call of a Web Service as defined by the SOAP specification ( with the help of the provided WSDL file.
  • A receiving Web Service on the server side in order to accept requests to deliver the results (CheckDeliverRequest, defined in the WSDL file). This is only necessary for the asynchronous interface.

Furthermore, you need a computer system with a fixed IP address from where the SOAP call is initiated, where the Web Service runs and which accepts the results if using the asynchronous API (Check Delivery Requests). This computer system must be reachable from the tyntec IP. For the fastest implementation and expert support from tyntec, we recommend implementing the GNV using:

 The following link to documents that are useful in implementing the Global Number Verification service with the above components: 

This is the overview of the workflow for querying phone number information:

In addition, the following information is relevant if you’re using the Asynchronous SOAP protocol:

As previously mentioned, tyntec’s SOAP implementation uses HTTP as its transport layer. The initial request consists of the number to be queried, in international format. The result will contain:

Number range holder network information (MCC/MNC)

  • Number range holder country
  • Number range holder country
  • Number range holder time zone

Subscription network information

  • IMSI network info (MCC/MNC)
  • IMSI country
  • IMSI time zone
  • HLR network information (MCC/MNC)
  • HLR country
  • HLR time zone

Servicing network information

  • MSC network information (MCC/MNC)
  • MSC country
  • MSC time zone


  • Presence information of the handset (true/false)
  • Roaming information (true/false)
  • Porting information (true/false)
  • SS7 network error code