Look up routing information
Request routing information for a North American telephone number. Use it to interpret available routing/carrier data, not as proof of subscriber identity, ownership, reachability or availability to purchase. A lookup can charge your account.
Request
Use your enabled API account and its allowed source IP address. Provide the complete number as digits including country code 1. The example uses environment variables and a fictional number. The handler does not normalize punctuation; validate the input before submitting.
curl --silent --show-error --user "$API_USER:$API_PASSWORD" \
https://api.multitel.net/v3/lrn/12025550123Response
Illustrative selected fields only; availability depends on the source and number type.
{
"status": {
"code": 200,
"msg": "Success"
},
"response": {
"lrn": "12025550123",
"ocn": "0000",
"local": 1,
"ported": 0,
"cost": "$0.00025"
}
}The standard lookup lowercases the returned field names. Carrier, rate-center, location and jurisdiction fields may be present depending on the source. The response is not a fixed complete subscriber record. The local flag may be numeric 1 or string 0. The handler calculates ported by comparing the returned routing number with the supplied telephone number; do not interpret it as a verified full porting history.
Price and retries
The reviewed handler applies an account debit of $0.00025 when it reaches its completion path and records the lookup. The returned cost normally includes the dollar sign as a string, rather than a bare numeric amount. No idempotency key is exposed. Repeating a request can create another charge.
For prepaid accounts the code checks for at least 0.00025 balance. Its insufficient-balance message currently mentions $5, which does not match that threshold. Read the failure as a balance rejection and confirm account funds before retrying.
Failures and incomplete success
Read both HTTP status and JSON status.code/status.msg. An empty standard lookup result returns API code 404. API code 403 can indicate insufficient prepaid balance.
A current toll-free error path can still debit the lookup amount and report API code 200 without useful routing fields; its cost can be incomplete. A 200 code alone therefore does not establish a usable lookup. Validate the fields needed by your application, reconcile uncertain charges with account billing records and contact support for incomplete results.
Toll-free handling differs between input lengths in the reviewed implementation. Prefer full international digits and confirm required toll-free coverage with support. Do not automatically retry a malformed or incomplete result, and do not rely on a routing lookup to decide that a number is safe or authorized to call.