post
https://lookup.engy-api.io/mnp
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
Introduction
MNPDB resolving API's are allowing you to discover information about a provided number by directly querying the mobile network portability databases.
Example response
[
{
"date": "2024-06-17T13:52:13.974Z",
"mcc": "222",
"mnc": "08",
"msisdn": "393200103102",
"omnc": "88",
"originalNetwork": {
"countryName": "Italy",
"countryPrefix": "39",
"networkName": "Wind"
},
"ported": true,
"portedNetwork": {
"countryName": "Italy",
"countryPrefix": "39",
"networkName": "Fastweb"
},
"price": 0,
"response": 0
}
]Each response contains the following information:
date- time when the request was executed (ISO8601)msisdn- the number for which the response has been returnedmcc- Mobile country code (learn more)mnc- Mobile network code (learn more)- the mobile network code to which the number currently belongs
omnc- Original network code- Returned in case the
portedflag istrue
- Returned in case the
originalNetwork(The network to which number belongs)countryNamecountryPrefixnetworkName
portedNetwork(The network to which the number belongs when ported)countryNamecountryPrefixnetworkName
ported- Denotes whether the number has been portedprice- The price for this requestresponse- The response indicating the success or failure (see below)
Response values
| Value | Description | Action |
|---|---|---|
| 0 | Success | ✈️ |
| 1 | General error | Repeating the request won't yield different result |
| 2 | Pricing not set | Contact |
| 3 | Out of balance | Contact |
| 4 | Throttled | Contact |
| 5 | Invalid number | Number length not valid |
| 6 | Not resolved | Number cannot be resolved due to missing coverage |
| 7 | Timeout | Number cannot be resolved due to timeout |
| 8 | Missing permissions | Contact |