Skip to content

REVERSE CALLER IDENTITY & CNAM LOOKUP

Reverse Phone Lookup API

Perform a reverse phone lookup to retrieve the registered name associated with a phone number. Validates the number, checks priority regional databases (IN, IL), and queries global CNAM networks.

Explore plans See how it works

50 free requests per application · monthly allowance.

LIVE API TRIAL

5 free live checks per IP every 24 hours · Sponsored by PayloadAPI

Checking live trial availability...

Use your own API key in the playground.
Create free account
Trust score
75 / 100
Versions
v1
Endpoints
1

02 THE BIGGER PICTURE

A phone number is more
than an anonymous caller.

When a phone number interacts with your business, identity matters. Who is behind the call? Is the number valid, and which telecommunications carrier operates the line? Is it an individual or a registered entity?

Reverse Phone Lookup API resolves those questions in a single low-latency call. The API evaluates regional databases for priority countries (IN, IL) and queries global CNAM networks to return the registered caller name, line type, carrier, and geographic details.

One number goes in. Verified caller identity comes back. You decide how that information protects and empowers your product.

Registered caller ID

Retrieve verified caller name or registered entity from telecom records.

Carrier & line classification

Identify the active telecommunications carrier and distinguish mobile, landline, and VoIP lines.

Priority regional databases

Direct priority lookup for India (IN) and Israel (IL) alongside global CNAM coverage.

Clean E.164 formatting

Standardize international formatting and location context into reliable application payloads.

03 PUT CONTEXT TO WORK

Small steps.
Useful possibilities.

Where this API can fit into your application. Your product controls the decisions that follow.

01 /

Real-time inbound lead enrichment.

Resolve caller name and business identity immediately when a prospect submits a form or dials in.

02 /

Fraud prevention & KYC triage.

Cross-reference user-supplied names with registered CNAM subscriber records to detect synthetic identities.

03 /

CRM contact hygiene.

Enrich existing customer records with accurate caller names, location, timezones, and line types automatically.

04 MADE FOR YOUR WORKFLOW

Your integration.
A straightforward start.

Choose an endpoint, subscribe, and connect your application key right in the request builder.

Endpoint documentation

GET /calleridvalidation

Validate phone number and lookup caller ID

Validates phone number and performs reverse caller ID lookup against regional and global CNAM databases.

Parameters

phone_numberRequired
query · string

Phone number in international E.164 format (e.g. +14155552671)

Integration facts

  • No provider credentials are exposed to you
  • Requests are metered against your plan
  • Captured bodies are encrypted and kept 7 days

AI & Coding Agents

One-click MCP & llms.txt

The PayloadAPI Edge Gateway automatically bridges this API into a JSON-RPC 2.0 MCP server at /reverse-phone-lookup-api/v1/mcp. Tool discovery (initialize, tools/list) is quota-free; tools/call executions meter against your active plan.

View /apis/reverse-phone-lookup-api/llms.txt
Add to .cursor/mcp.json
{
  "mcpServers": {
    "payloadapi-reverse-phone-lookup-api": {
      "url": "https://gateway.payloadapi.com/reverse-phone-lookup-api/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${env:PAYLOADAPI_KEY}"
      }
    }
  }
}

Synthesized MCP tools (1)

get_calleridvalidationGET /calleridvalidation
Required: phone_number

MCP tool — Validate phone number and lookup caller ID

Live request

Request builder

Your first request starts here

Try Reverse Phone Lookup API with a free account.

50 free requests per application · monthly allowance. Create an account, connect an application, and activate your plan right here.

No payment details needed for this free allowance.

This endpoint does not accept a request body.

Sending calls the gateway for real: it authenticates your key, counts the request against your plan, and returns whatever the provider returns.

curl --request GET 'https://gateway.payloadapi.com/reverse-phone-lookup-api/v1/calleridvalidation' --header "Authorization: Bearer $PAYLOADAPI_KEY" --header 'Content-Type: application/json' --header 'X-Payload-Trace: enabled'

Streamed response

Response

Send a request to inspect status, headers, timing, cost, and streamed body chunks.

05 A PLAN FOR YOUR NEXT STEP

Start with the right plan.

Choose a plan for your application. New here? Create your first application and get its API key as part of setup, right on this page.

LIVE PLAN01

Free

$0.00USD · Free allowance
  • 50 requests per application
  • Monthly allowance · subscription anniversary
  • No payment or overage charges

Prices are shown in each plan’s published currency. Default usage rates can be overridden for individual endpoints.

06 GOOD TO KNOW

The details
before you begin.

Trust breakdown (75/100)View signals
  • Upstream safety30 / 30 ptsPassed

    Upstream origin and hosts passed all safety, allowlist, and SSRF restrictions.

  • Specification completeness10 / 25 ptsNeeds attention

    Endpoints manually defined without an OpenAPI specification.

  • Duplicate protection20 / 20 ptsPassed

    No name or upstream host collision detected against published listings.

  • Provenance & standing15 / 25 ptsNeeds attention

    Verified organization under review evaluation.

How do I get started?

Choose an available plan here. Select an existing application or create your first one during setup, save its API key, and activate your plan. Then use the key in the request builder. Requests call the gateway for real and count against your plan.

Do free requests reset every month?

Check the allowance period on each plan. A one-time allowance does not reset. A monthly free allowance renews on the subscription anniversary. Free allowances are per application.

Does reverse phone lookup guarantee caller identity worldwide?

Reverse phone lookup queries authoritative telecom databases and global CNAM carrier records. Coverage prioritizes local databases in regions like India (IN) and Israel (IL) with global CNAM coverage elsewhere. Name availability depends on regional telecommunication registries and subscriber privacy settings.

Why are some plans unavailable for activation?

Their published pricing is available for comparison. Free allowances can be activated here; commercial plans with active checkout can be purchased. Custom enterprise tiers require contacting the provider directly.

What does the trust score tell me?

The score summarizes recorded catalog verification checks. Review the breakdown for individual signals; it is not an uptime or performance guarantee.

Back to top ↑