MNP Supplier HTTP API
The MNP Supplier HTTP API provides an efficient way to retrieve MCC and MNC information of a recipient mobile subscriber by sending querying to MNP HTTP Service developed by MNP Supplier (MNP Source further).
The subject domain of an endpoint URL is:
https://{your mnp api server domain name}/horisen-mnp/v1
This document describes necessary parameters and samples to demonstrate users how to use the HORISEN MNP Supplier HTTP API for new MNP Source development.
1. Authentication
All API calls require authentication. This is essential for the API to identify which user is making the call so that appropriate results will be returned, as well as for security reasons.
For this purpose, MNP Supplier can use VPN access to their MNP HTTP Service or should use Basic authorization.
Authentication data are sent via HTTP header "Authorization".
Steps to construct authorization header:
- Base64 encode the API Key.
- Supply an "Authorization" header with content "Basic" followed by the encoded API Key.
Example:
Authorization = "Basic Base64(APIKey)"
Request an API Key from our support team. Please keep your API Key safe to prevent any unauthorized access. Once you obtain your API Key, you will have to use it in every API call you make.
2. Versioning
HTTP API will support versioning through URI Path.
Example:
- Version 1:
https://{your mnp api server domain name}/horisen-mnp/v1 - Version 2:
https://{your mnp api server domain name}/horisen-mnp/v2
Where {your mnp api server domain name} can be your public domain name or public/private IP:port if you will use VPN access.
And horisen-mnp is base path for HORISEN MNP Supplier HTTP API.
Please keep in mind that currently only v1 is supported.