Number intelligence

Local routing number lookups

Use LRN information to support routing, rating and number-portability decisions.

A flat price for routing lookups

$0.00025 per query

USD. One thousand queries cost $0.25; one million cost $250. The same query rate applies at every volume—there are no volume discounts.

Maintain sufficient account balance and use an approved API account. Number rental, calling and other lookup services are separate charges.

Set up API access — sign in

Which number should the call use for routing?

An LRN identifies the routing number associated with a telephone number. A ported number can retain its dialed number while its routing information changes. Use the result in your routing and rating workflow.

Query the telephone number in international format. An ANI argument is optional for the LRN operation; it is not required for a basic lookup.

Make your first LRN request

curl --user "USERNAME:PASSWORD" \
  "https://api.multitel.net/v3/lrn/12025550123"

Replace the credentials and example telephone number. Keep credentials on your application server, outside public website code.

Read the complete LRN reference

Interpret the response

lrn
The routing number returned for the queried telephone number.
ported
Whether the result identifies the number as ported.
ocn
The operating-company identifier, when returned.
lata
The Local Access and Transport Area identifier.
rc
The rate center associated with the result.

Check the API response status before using its data. Fields can be absent or empty; handle those cases in your application.

Service capabilities

01

Identify the routing number associated with a telephone number

02

Support least-cost routing and rating workflows

03

Integrate lookups into your own applications

LRN lookups cost $0.00025 per query with no volume discounts. Optional lookup services and their required fields are separate.

How to get started

  1. Review the flat query price and required response fields.

  2. Configure approved API access.

  3. Use the returned number information in your routing workflow.