MCC-MNC API
The MCC-MNC API lets partners resolve mobile network operators by MCC/MNC , PLMN , country ISO , dial code , or operator name . Use it to enrich phone numbers, validate roaming data, or power operator lookup in your applications.
Base URL: https://api.omaxtelecom.com/tools/mcc-mnc/
What can you do?
Capability Endpoint Description Operator lookup POST /lookupResolve a single operator by MCC+MNC or PLMN By country POST /by-countryList operators for an ISO country code or dial prefix Search POST /searchSearch operators by name (min. 2 characters) Bulk lookup POST /bulk/lookupSubmit a batch lookup job (async) Job status GET /bulk/lookup/{job}Poll bulk job progress and results Health GET /healthCheck service availability (no auth)
Authentication
All endpoints except /health require OAuth 2.0 Client Credentials via OmaxTelecom ID :
Authorization: Bearer <access_token>
Obtain a token from the shared OmaxTelecom API auth endpoint. This is not under the MCC-MNC base URL — see the Auth API reference :
POST https://api.omaxtelecom.com/auth/token
Content-Type: application/x-www-form-urlencoded
grant_type=client_credentials&client_id={client_id}&client_secret={client_secret}
Get your client_id and client_secret from OmaxTelecom Console .
Billing
Each successful lookup , by-country , or search request is billed per your organisation's price_per_request via the Console Wallet API when the price is greater than zero.
HTTP status Error code Meaning 402INSUFFICIENT_BALANCEWallet balance too low 403MCC_MNC_DISABLEDMCC-MNC API not enabled for your organisation 403BILLING_NOT_CONFIGUREDBilling is not configured 404OPERATOR_NOT_FOUNDNo matching operator
Response envelope
Successful responses:
{
"success" : true ,
"data" : {
"mcc" : "242" ,
"mnc" : "99" ,
"plmn" : "24299" ,
"region" : "Europe" ,
"country" : "Norway" ,
"iso" : "NO" ,
"dial_code" : "+47" ,
"dial_codes" : [ "+47" ],
"operator" : "TampNet AS" ,
"brand" : null ,
"tadig" : "NORTM" ,
"bands" : "LTE 800, LTE 1800"
}
}
Error responses:
{
"success" : false ,
"error" : {
"code" : "OPERATOR_NOT_FOUND" ,
"message" : "No operator matched the request"
}
}
Operator object
Field Description mccMobile Country Code mncMobile Network Code plmnCombined PLMN (MCC + MNC) regionGeographic region countryCountry name isoISO 3166-1 alpha-2 country code dial_codePrimary international dial prefix dial_codesAll dial prefixes for the country operatorNetwork operator name brandCommercial brand (if different) tadigTADIG code (roaming) bandsSupported frequency bands
Examples
Lookup by MCC and MNC
curl -X POST "https://api.omaxtelecom.com/tools/mcc-mnc/lookup?mcc=242&mnc=99" \
-H "Authorization: Bearer <access_token>"
Response 200 OK:
{
"success" : true ,
"data" : {
"mcc" : "242" ,
"mnc" : "99" ,
"plmn" : "24299" ,
"region" : "Europe" ,
"country" : "Norway" ,
"iso" : "NO" ,
"dial_code" : "+47" ,
"dial_codes" : [ "+47" ],
"operator" : "TampNet AS" ,
"brand" : null ,
"tadig" : "NORTM" ,
"bands" : "LTE 800, LTE 1800"
}
}
Response 404 Not Found:
{
"success" : false ,
"error" : {
"code" : "OPERATOR_NOT_FOUND" ,
"message" : "No operator matched the request"
}
}
Lookup by PLMN
curl -X POST "https://api.omaxtelecom.com/tools/mcc-mnc/lookup?plmn=24299" \
-H "Authorization: Bearer <access_token>"
Returns the same operator object as the MCC+MNC lookup above.
List operators in Norway
curl -X POST "https://api.omaxtelecom.com/tools/mcc-mnc/by-country?iso=NO" \
-H "Authorization: Bearer <access_token>"
Response 200 OK:
{
"success" : true ,
"data" : {
"iso" : "NO" ,
"dial_code" : "+47" ,
"count" : 2 ,
"operators" : [
{
"mcc" : "242" ,
"mnc" : "01" ,
"plmn" : "24201" ,
"region" : "Europe" ,
"country" : "Norway" ,
"iso" : "NO" ,
"dial_code" : "+47" ,
"dial_codes" : [ "+47" ],
"operator" : "Telenor Norge AS" ,
"brand" : "Telenor" ,
"tadig" : "NORTM" ,
"bands" : "GSM 900, UMTS 2100, LTE 800"
},
{
"mcc" : "242" ,
"mnc" : "02" ,
"plmn" : "24202" ,
"region" : "Europe" ,
"country" : "Norway" ,
"iso" : "NO" ,
"dial_code" : "+47" ,
"dial_codes" : [ "+47" ],
"operator" : "Telia Norge AS" ,
"brand" : "Telia" ,
"tadig" : "NORTL" ,
"bands" : "GSM 900, UMTS 2100, LTE 800"
}
]
}
}
Search operators by name
curl -X POST "https://api.omaxtelecom.com/tools/mcc-mnc/search?query=Telenor&iso=NO&limit=10" \
-H "Authorization: Bearer <access_token>"
Response 200 OK:
{
"success" : true ,
"data" : {
"query" : "Telenor" ,
"iso" : "NO" ,
"limit" : 10 ,
"count" : 1 ,
"operators" : [
{
"mcc" : "242" ,
"mnc" : "01" ,
"plmn" : "24201" ,
"region" : "Europe" ,
"country" : "Norway" ,
"iso" : "NO" ,
"dial_code" : "+47" ,
"dial_codes" : [ "+47" ],
"operator" : "Telenor Norge AS" ,
"brand" : "Telenor" ,
"tadig" : "NORTM" ,
"bands" : "GSM 900, UMTS 2100, LTE 800"
}
]
}
}
Bulk lookup
curl -X POST "https://api.omaxtelecom.com/tools/mcc-mnc/bulk/lookup" \
-H "Authorization: Bearer <access_token>" \
-H "Content-Type: application/json" \
-d '{"items": [{"mcc": "242", "mnc": "01"}, {"plmn": "24299"}]}'
Response 202 Accepted:
{
"success" : true ,
"data" : {
"job_id" : "9f3c2b1a-7d6e-4f5a-8b9c-0d1e2f3a4b5c"
}
}
Poll the job:
curl "https://api.omaxtelecom.com/tools/mcc-mnc/bulk/lookup/9f3c2b1a-7d6e-4f5a-8b9c-0d1e2f3a4b5c" \
-H "Authorization: Bearer <access_token>"
Response 200 OK (processing):
{
"success" : true ,
"data" : {
"job_id" : "9f3c2b1a-7d6e-4f5a-8b9c-0d1e2f3a4b5c" ,
"status" : "processing" ,
"total_count" : 2 ,
"processed_count" : 1 ,
"failed_count" : 0 ,
"items" : [
{
"plmn" : "24201" ,
"status" : "completed" ,
"result" : {
"mcc" : "242" ,
"mnc" : "01" ,
"plmn" : "24201" ,
"region" : "Europe" ,
"country" : "Norway" ,
"iso" : "NO" ,
"dial_code" : "+47" ,
"dial_codes" : [ "+47" ],
"operator" : "Telenor Norge AS" ,
"brand" : "Telenor" ,
"tadig" : "NORTM" ,
"bands" : "GSM 900, UMTS 2100, LTE 800"
},
"error" : null
},
{
"plmn" : "24299" ,
"status" : "pending" ,
"result" : null ,
"error" : null
}
]
}
}
Health check
curl "https://api.omaxtelecom.com/tools/mcc-mnc/health"
Response 200 OK:
{
"ok" : true ,
"timestamp" : "2026-08-20T16:42:00+00:00"
}
Getting started
Enable MCC-MNC access for your organisation in OmaxTelecom Console .
Obtain an access token via OmaxTelecom ID using your client_id and client_secret.
Call GET /health to confirm the service is reachable.
Start with POST /lookup or POST /search for single lookups.
Use bulk endpoints when you need to process large operator lists asynchronously.
API Documentation
Need Help?
Contact support@omaxtelecom.com for integration support.
Last modified on September 17, 2026