Number Lookup API

Number Lookup API for messaging, routing and fraud teams.

Live carrier data and MCC/MNC for E.164 numbers worldwide. Single lookups or bulk jobs of up to 1,000 numbers.

From €0.0065 per query, same rate for all countries. REST API with OAuth 2.0. Production credentials are issued after account verification (KYC).

Built for

Built for messaging, fraud and data teams

Retrieve live carrier data and MCC/MNC to improve messaging routing, fraud prevention, and data enrichment.

Cut wasted SMS spend

Skip numbers with wrong format before sending. Reduce failed deliveries and lower messaging costs.

Fraud screening

Retrieve live carrier data and MCC/MNC during sign-up and flag numbers that do not match the expected network or country.

Clean CRM and contact lists

Enrich contact databases with carrier metadata. Improve data quality before campaigns.

Route A2P traffic by network

Resolve the current network behind a number, before choosing an SMS or voice route.

Architecture

Lookup flow: token in, carrier data out

Authenticate with OAuth 2.0 client credentials, then look up one number or queue a bulk job of up to 1,000 numbers.

Number Lookup API request flow Your backend exchanges its client ID and secret for a short-lived Bearer token at POST /auth/token, then sends single lookups or bulk jobs of up to 1,000 E.164 numbers to the Number Lookup API. Each result returns the current carrier, line type and MCC/MNC as JSON, ready to enrich your own records. OAuth 2.0 client credentials · Bearer token on every request · JSON responses Your stack OmaxTelecom Bearer token (5 min) Bearer · request live query JSON: carrier · line type · MCC/MNC Your backend sign-up · CRM · routing Your records enriched with carrier data POST /auth/token OAuth 2.0 client credentials Number Lookup API single · bulk ≤ 1,000 Carrier data live carrier · MCC/MNC Production credentials are issued after account verification (KYC). One price per query for every country.
Reading the diagram Your backend exchanges its client ID and secret for a short-lived Bearer token at POST /auth/token, then sends single lookups or bulk jobs of up to 1,000 E.164 numbers to the Number Lookup API. Each result returns the current carrier, line type and MCC/MNC as JSON, ready to enrich your own records.

Technical details

API features

Developer-friendly REST API built for real-time validation and high-volume batch processing.

Real-time single lookup

POST a single E.164 phone number and receive a carrier lookup result in the response.

POST /number-lookup

Async bulk jobs

Queue bulk carrier lookups with up to 1,000 unique E.164 numbers per request. Poll for results when ready.

POST /number-lookup/bulk

OAuth 2.0 client credentials

Secure authentication via RFC 6749 Client Credentials grant. Bearer tokens with 5-minute expiry.

POST /auth/token

One global price

€0.0065 per query across all countries. No per-destination rate tables.

Health endpoint

Public service health check at GET /number-lookup/health. No authentication required.

GET /number-lookup/health

Org-scoped job polling

Bulk jobs are scoped to your organisation. Poll status and retrieve results securely via job ID.

GET /number-lookup/bulk/{job_id}

Quick start

Your first lookup

One authenticated request returns the carrier data for a number.

Full API reference at developer.omaxtelecom.com

$ curl -X POST https://api.omaxtelecom.com/numbers/number-lookup \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "phone_number": "+447700900123" }' // Response{ "success": true, "data": { /* carrier lookup result */ }}

Prices

One price for every country

No per-destination rate tables.

Every country

€0.0065

per lookup query

Same price for every country. Single and bulk lookups billed per request.

Each request is charged when price_per_lookup is greater than zero, including cached results. Indicative. Final rates depend on volume. Ask for a volume quote.

Integration

Onboarding

From account verification to carrier lookups at scale.

  1. Step 01: Account and KYC

    Open an account and complete company verification. API credentials (Client ID and Client Secret) are issued for production use after verification.

  2. Step 02: Authenticate and look up

    Exchange credentials for a Bearer token via OAuth 2.0 Client Credentials. Send a single lookup or queue a bulk job.

  3. Step 03: Scale with bulk jobs

    Submit up to 1,000 unique E.164 numbers per bulk request. Poll job status until completed and retrieve per-number results.

FAQ

Technical questions

The Number Lookup API uses OAuth 2.0 Client Credentials (RFC 6749 §4.4). Exchange your Client ID and Client Secret from the OmaxTelecom Console for a Bearer access token at POST /auth/token. Include the token in the Authorization header for all lookup requests.

Single lookup (POST /number-lookup) returns a carrier result for one E.164 phone number immediately. Bulk lookup (POST /number-lookup/bulk) queues an async job for up to 1,000 unique numbers and returns a job_id. Poll GET /number-lookup/bulk/{job_id} until status is completed or failed.

All phone numbers must be in E.164 format: a leading plus sign followed by the country code and subscriber number (e.g. +447700900123). Numbers must match the pattern ^\+[1-9]\d{1,14}$.

Each lookup is charged at €0.0065 when price_per_lookup is greater than zero. Billing applies per request regardless of whether the result is served from cache. For high volumes, ask us for a quote.

Yes. GET /number-lookup/health is a public endpoint that returns whether the service is globally operational. No authentication is required.

Complete documentation including request and response schemas is in the API reference at developer.omaxtelecom.com. Production credentials are issued after account verification (KYC).

Ready to verify numbers at scale?

Tell us about your traffic and we'll come back within one business day with pricing and onboarding steps.

  • Business accounts only
  • KYC required before production
  • Prepaid wallet