Carrier lookup API

Carrier lookup API for US and Canadian phone numbers

See which carrier serves a US or Canadian number today, with its OCN, its routing number (LRN) and whether it was ported. The answer comes from a live carrier dip at lookup time, so a number that switched carriers last week shows the new one.

  • US and Canadian numbers
  • Live carrier dip
  • One credit per lookup
One lookup: (312) 555-0142
Carrier now
AT&T dipCarrier
Ported
Yes dipPorted
Routing number
312-555-0199 dipLrn
Carrier ID (OCN)
6010 dipOcn
Line type
Mobile, wireless dipCarrierSubType
Numbering plan says
Verizon nanpCarrier

Fictional 555 number. The numbering-plan answer is out of date once a number ports.

What a carrier lookup returns

Every lookup returns these carrier fields. Values are strings, booleans included.

FieldExampleMeaning
dip"success"Status of the carrier dip: "success", "error" or "invalid".
dipCarrier"AT&T"The carrier serving the number now.
dipCarrierType"mobile"Broad carrier type: "mobile", "landline", "invalid" or "undefined".
dipCarrierSubType"WIRELESS"Sub-type such as WIRELESS, PCS, ILEC, RBOC, CLEC or IPES (VoIP). The docs list every code.
dipOcn"6010"Operating Company Number: the ID of the carrier operating the number now.
dipLrn"3125550199"Local Routing Number: the number calls and texts are actually routed on. This is what changes when a number ports.
dipPorted"true""true" when dipLrn differs from the number itself, the standard way to detect a port.
nanpCarrier"verizon"Carrier according to numbering-plan data. Not reliable once a number ports, so prefer dipCarrier.

Why a live carrier dip matters for ported numbers

Numbering-plan data tells you which carrier a block of numbers was assigned to. Once a subscriber ports their number to another carrier, that answer is out of date, and anything built on it inherits the error: SMS routing, carrier-based fraud rules, line-type filters.

We return both views. nanpCarrier is the numbering-plan answer. The dip* fields come from a live carrier dip at lookup time: when the routing number differs from the number itself, dipPorted is "true", dipLrn holds the routing number, and dipCarrier and dipOcn name the carrier the number moved to.

Same number, two answers
  • Numbering plan nanpCarrier
    Verizon The carrier the number block was assigned to. Stale after a port.
  • Live carrier dip dipCarrier
    AT&T The carrier serving the number now, with dipPorted: "true" and the new routing number in dipLrn.

Fictional (312) 555-0142, the number in the sample below.

Example request and response

Send the number in any common format. Add ip to get IP-based location too.

This is the response for a ported mobile: dipLrn differs from subscriber, so dipPorted is "true". Field names and formats match the live API.

Request

curl --request POST \
  --url 'https://api.checkthatphone.com/v1/lookup' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{"phone": "(312) 555-0142"}'

credits_used: 1 is the whole cost of this call. The Node.js and Python SDKs and every row of a bulk CSV upload return the same fields.

Highlighted fields in the response: dipLrn, dipPorted, dipOcn, dipCarrier, dipCarrierSubType, dipCarrierType.

{
  "success": true,
  "credits_used": 1,
  "data": {
    "subscriber": "3125550142",
    "optDate": "2026-10-03T15:04:12.381Z",
    "action": "send",
    "deliverable": "true",
    "reason": "",
    "nanpType": "mobile",
    "blackList": "false",
    "dip": "success",
    "dipLrn": "3125550199",
    "dipPorted": "true",
    "dipOcn": "6010",
    "dipCarrier": "AT&T",
    "dipCarrierSubType": "WIRELESS",
    "dipCarrierType": "mobile",
    "geoState": "IL",
    "geoCity": "chicago",
    "geoCountry": "US",
    "geoSource": "area-code",
    "timezone": "America/Chicago",
    "tzOffset": 6,
    "error": "false"
  }
}

What else comes back in the same call

Carrier data is one part of every lookup. The same credit also pays for these.

  • Line type

    nanpType plus the carrier type and sub-type: mobile, landline or VoIP. The line type lookup API page shows how to read them.

    nanpTypedipCarrierTypedipCarrierSubType
  • Deliverability

    A send-or-not answer for texts with the reason, a recent carrier deactivation check (up to 45 days) and our internal blacklist.

    actiondeliverablereasondeactivationDateblackList
  • Location

    State, city, metro and time zone from the area code. Pass an ip and we add ipResult and IP-based location.

    geoStategeoCitytimezoneipResult
  • Opt-in add-ons

    The TCPA litigator scrub (+1 credit), the landline SMS lookup (+1 credit, landlines only) and free state DNC and complainer checks.

    litigatordipMessagingEnableddncStateResult

Where teams use carrier data

Pricing

Carrier data comes with every lookup, with no per-field fees: one lookup is one credit.

  • Free $0/mo 500 lookups included Hard cap, no overage
  • 1K $5/mo 1,000 lookups included Then $0.005 each
  • 10K $30/mo 10,000 lookups included Then $0.003 each
  • 100K $100/mo 100,000 lookups included Then $0.001 each
  • 500K $450/mo 500,000 lookups included Then $0.0009 each

Failed lookups are free. Annual billing is 15% off. Above 500,000 lookups a month, ask for a volume quote. Every detail is on the pricing page.

Limits worth knowing

  • US and Canada only

    NANP numbers only. For other countries, use a global provider.

  • Not a reassignment check

    deactivationDate shows a recent carrier deactivation (up to 45 days), not who holds the number once that time has passed.

  • Not a delivery guarantee

    deliverable is a reachability summary, not a live delivery test, and carriers don't guarantee delivery.

Carrier lookup: common questions

What is a carrier lookup API?

An API that tells you which carrier serves a phone number. The CheckThatPhone carrier lookup returns the current carrier, OCN, routing number (LRN), porting status and line type for US and Canadian numbers, from a live carrier dip, in one POST /v1/lookup call.

Does the carrier lookup detect ported numbers?

Yes. dipPorted is "true" when the routing number (dipLrn) differs from the number itself, and dipCarrier names the carrier the number moved to. nanpCarrier comes from numbering-plan data and can be out of date after a port, so prefer dipCarrier.

Does it work for Canadian numbers?

Yes. The API accepts US and Canadian (NANP) numbers in any common format: 10 digits, or 11 digits starting with 1. Numbers outside North America are not supported.

How much does a carrier lookup cost?

One credit. There is no separate carrier fee. The Free plan includes 500 credits a month, hard-capped; paid plans start at $5 a month for 1,000 credits, and overage goes down to $0.0009 per credit on the 500K plan. Failed lookups are not billed.

Can I try it without writing code?

Yes. Run a free check with the demo on the homepage. For a whole list, sign up and upload a CSV from the dashboard: see bulk phone validation.

Try it on your list

The Free plan includes 500 lookups a month, hard-capped. Paid plans start at $5 a month.