Number Lookup Line Type Intelligence

1.   The data for non-US/CA are not port corrected. What are the values of these data?

1. Cost efficiency: Non-port corrected data is significantly cheaper than real-time HLR lookups because it doesn’t require access to live network feeds. 
2. Performance and Scalability: Without the need for real-time lookup, non-port corrected data offers faster lookup times, making it highly scalable for bulk operations. 
3. Workflow optimization: If the a number is ported, the line type will remain the same. Enterprise can categories the numbers based on line type attributes for campaign targeting and fraud mitigations.
4. Routing value: For customer requires live routing, non-ported corrected data is not designed for it, it can still meet basic routing needs.

2.   What is the rate limit for the Number Lookup API?

To enhance our service efficiency, we have implemented a rate-limiting mechanism for the Number Lookup API.

The Number Lookup API offers three tiers to cater to different customer needs. If premium or custom tier is required, please contact us to enable it.

3. Is Number Lookup subject to HIPAA compliance?

No, Number Lookup is not subject to HIPAA because it does not process, store, or associate phone numbers with health-related data. While telephone numbers are considered PHI, HIPAA only applies when they are linked to medical information. Since Number Lookup does not process PHI, a Business Associate Agreement (BAA) is not required. 

4. Why do you need use case approval for Line type feature enablement?

In the US, the data we use comes from the NPAC (Number Portability Administration Center). NPAC has strict contractual terms and conditions that govern its usage. To remain contractually compliant with our supply agreements, we must ensure customers declare their intended use of this data.

5. Why am I not getting the correct carrier after porting my number? Is the data wrong because the operator is different?

In nearly all countries, numbers are assigned by the regulator to an operator, and this assignment is persistent. We use this persistent relationship to define the line type, and it does not change.

When a number is ported to a different operator, it is essentially loaned to the new operator, but the original operator assignment remains the same.

If the number is ported again or disconnected, it is typically returned to the original operator before any further action is taken.
 

Learn more about the Number Lookup API.