Skip to content

A LITTLE MORE CLARITY IN EVERY NUMBER

Phone Number checker API

Identify the carrier, line type (mobile / landline / VoIP), validity, and formatting for any phone number worldwide. Clean JSON, one fast request per number.

Explore plans See how it works

500 free requests per application · one-time 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 a string of digits.

When a number enters your product, context matters. Is it valid? Which carrier is associated with it? Is it a mobile number, a landline, or VoIP? And how should it be formatted?

Phone Number Checker brings those details into a single API request. Use the returned data to add context to contact records, inform your application’s rules, and handle phone numbers more consistently across your product.

One number goes in. Structured JSON comes back. You decide how that information fits your workflow.

Check validity

Understand the validity of a supplied phone number.

Identify the carrier

Add carrier information to the context you have about a number.

Know the line type

Distinguish mobile, landline, and VoIP numbers in your workflow.

Standardize formatting

Use formatting information to keep your contact data consistent.

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 /

A clearer first interaction.

Add a validation step to a contact form or onboarding flow. Use the number’s validity and formatting information to guide how your application handles the entry.

02 /

Contact records with more context.

Enrich a CRM record with carrier and line-type information. Bring a more consistent representation of phone numbers into the systems your team uses.

03 /

Rules that consider the number.

Use mobile, landline, or VoIP classification as an input to your application logic. Combine it with your own business rules and other relevant signals.

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 /api/v1/phonevalidation

Version v1 · REST. Calls route through the gateway as /phone-number-checker-api/v1/api/v1/phonevalidation.

Parameters

phone_numberOptional
query · string

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 /phone-number-checker-api/v1/mcp. Tool discovery (initialize, tools/list) is quota-free; tools/call executions meter against your active plan.

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

Synthesized MCP tools (1)

get_api_v1_phonevalidationGET /api/v1/phonevalidation
No required parameters

MCP tool — GET /api/v1/phonevalidation

Live request

Request builder

Your first request starts here

Try Phone Number checker API with a free account.

500 free requests per application · one-time 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/phone-number-checker-api/v1/api/v1/phonevalidation' --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

PAYASGO

$0.0002USD · default rate per request
  • No included allowance published
  • No recurring fee
  • $0.0002 USD default usage rate per request
LIVE PLAN02

Free

$0.00USD · Free allowance
  • 500 requests per application
  • One-time allowance · does not reset
  • No payment or overage charges

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

DO THE NUMBERS

A quick usage estimate.

Based on PAYASGO’s default rate. Endpoint-specific rates and taxes are not included.

$2.00USD estimated usage

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 validation verify who owns a number?

No ownership verification capability is described for this API. A phone-number check provides context about the number; it does not prove that a person controls it.

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 ↑