POST /api/v1/checkcurl -X POST "https://api.carrierlookup.online/api/v1/check" \
-H "X-API-Key: sk_your_api_key" \
-H "Content-Type: application/json" \
-d '{ "service_type": "carrier", "identifier": "+12345678900" }'Find the carrier a number was originally allocated to, with line type and location.
POST /api/v1/checkNo sign-in required.
Send one number and select this product with service_type. Authentication uses your API key.
Copy the curl command below and replace only the example API key with your own.
POST /api/v1/checkcurl -X POST "https://api.carrierlookup.online/api/v1/check" \
-H "X-API-Key: sk_your_api_key" \
-H "Content-Type: application/json" \
-d '{ "service_type": "carrier", "identifier": "+12345678900" }'200 OK{
"code": 0,
"msg": "ok",
"data": {
"service_type": "carrier",
"identifier": "+12345678900",
"carrier": "T-Mobile",
"underlying_carrier": "",
"number_type": "Fixed Line or Mobile",
"country_code": "US",
"region": "OH",
"city": "AKRON"
}
}Send the number in E.164 form: a plus sign, the country code, then the subscriber number with no spaces or separators — for example +12345678900.
The SaaS dashboard and the synchronous API return the same response shape, carrying the original carrier and related fields.
A successful response returns the carrier fields synchronously. They describe the original allocation, which porting does not change, so running the lookup again will not reveal a later carrier. Obtain consent separately before contacting anyone.
carrier · string — Carrier the number was originally allocated to. Not the current carrier after porting.underlying_carrier · string — Underlying carrier reported by the provider when it differs from the allocated one; empty string when the provider does not supply one.number_type · string — Line type reported by the provider; empty when unavailable.country_code · string — ISO country code the number belongs to.region · string — Allocation region; empty when the provider does not supply one.city · string — Allocation city; empty when the provider does not supply one.Read the carrier a number was originally allocated to and its line type before running later internal routing rules.
Write the original carrier and allocation region into cost models or procurement records to review expected number-range costs.
Compare a number's allocation, country and region with existing contact records to find missing or inconsistent data.
Group number lists by original carrier, line type and allocation region so later data work has clear dimensions.
Original Carrier Lookup returns the carrier the number was originally allocated to, its line type and the region it belongs to. Use service_type carrier (the parameter that selects a product) with one number in E.164 form, for example +12345678900, and read the carrier fields in the same API response.
It checks one number and returns the carrier the number was originally allocated to, its line type and the region it belongs to in the same synchronous response.
Balance is charged only for completed checks. Failed or undetermined checks do not keep the charge.
Submit one number in E.164 form, for example +12345678900. The country code is part of the number, so you do not select a country separately.
No. It only reports the network a number was originally allocated to; it does not follow porting and does not mean the number is reachable. Consent and applicable rules remain your responsibility.
Create an account to use every product from the SaaS dashboard or the API: realtime checks and async bulk checks draw on the same balance.