Prefix-based lookup
Phone numbers are normalized before matching the most specific reference prefix.
Enrich your business workflows with number types, providers, and reference regions through prefix-based HLR lookup.
Solution scope
The HLR API supports phone-number reference data integration. Results depend on the available dataset and mappings, rather than a live check on an operator's network.
Phone numbers are normalized before matching the most specific reference prefix.
Number types, providers, and city or area-code references based on available mappings.
Discuss response formats, API access, and usage policies for your application.
The scope above is a starting point for discussing your needs. Features, schedules, integrations, and implementation quotes are confirmed with the billio team.
Integration overview
This example shows how lookup information can be structured. Production fields and API contracts follow the agreed integration documentation.
{
"success": true,
"data": {
"prefix": "08xx",
"number_type": "MOBILE",
"provider": "Illustrative provider",
"region": "Reference region"
},
"meta": {
"dataset": "illustration"
},
"error": null
}{
"number": "08xxxxxxxxxx"
}Illustrative data. No phone number is submitted or looked up.
Who it's for
Add phone-number reference information to your application workflows.
Support phone-number classification using prefix reference data.
Include phone-number reference data in your data checks.
Workflow overview
The system accepts and normalizes the number format according to the agreed rules.
The canonical resolver uses longest-prefix matching against the applicable reference data.
Mapping information is returned in a structured API response.
Let's talk
Tell us what you need so we can discuss the right scope for your solution.