FAQ | Verify

Utilize tyntec’s FAQs to help solve any issues you may have. Additionally, learn about cloud communications, CPaaS, SMS for business, authentication, and more. If any questions arise while reading, don’t hesitate to contact us.

What Number Format Should Be Used for the Number Information APIs?

FAQs

Verify

General

Overview

What Can I Do With Number Information and What Service Should I Choose?

What Information Does the Number Verification Provide?

How Does Number Verification Prevent Fraud?

What Interfaces Are Available for Number Information APIs?

What’s Your Throughput for the Number Information APIs?

How Are Number Lookup Requests Billed?

What Number Format Should Be Used for the Number Information APIs?

How Long Will It Take for Me to Get a Number Information Query Response?

Are Multiple Requests for the Same Number Allowed?

What Is a ‘Source IP Address’?

Can I Add Multiple ‘Source IP Addresses’ ?

What Is the ‘Respond Back Url’?

What Is the Difference Between the Restful API and Enum?

How Can I Create My tyntec Phone Verification Account?

Phone Verification

Overview

What Information Does the Phone Verification Service Provide?

What Do the Return Values of the Phone Verification API Mean?

How Soon Can I Start Using the Phone Verification Service?

Portability Check

Overview

What Information Does the Portability Check Provide?

Where Can I Find the Technical Documentation for Portability Check?

How Soon Can I Start Using the New Portability Check Account?

What Does the Acknowledgement Receipt Look Like?

What number format should be used for the Number Information APIs?

The phone number provided to our Number Information APIs should be in the international format following the standard E.164 rules.

These are examples of acceptable phone numbers:

  • 491622943176

  • +491622943176

  • 00491622943176

If a phone number is not in an acceptable format, as shown above, the API will reject it. You will not be charged for this attempt.