1NCE offers an Application Programming Interface (hereinafter referred to as “API”) that allows users to implement the most important functions of the Customer Portal into a customer’s environment. The supported functions of the 1NCE API generally enables the customer to manage, control and monitor the 1NCE SIM Cards from an external system.
The 1NCE API can be found under the following link:
To get the 1NCE API started the customer needs to authenticate himself. This can be done by clicking on the „Authorize“-button. The customer is asked to enter his credentials, which as an “Owner” typically are the same credentials as the one for the 1NCE Customer Portal (e-mail address and password). As an “API User” these credentials are the client ID, with the account number as a prefix, and the related client secret.
Afterwards, you can try the different requests of the 1NCE API, which are as follows:
Get a List of Orders
Post an order
Get a single Order, identified by its order number
Get a list of products
Get a List of SIM Cards
Change a list of SIM Cards for activate, deactivate, label, IMEI lock, etc.
Get status information i.e. status, label, MSISDN, IMSI, ICCID, Lifetime, for a device with an ICCID
Modification of a SIM Card to activate, deactivate, change label, change IMEI lock, etc.
Retrieve connectivity information and location for a SIM
Get diagnostic/event information for a SIM Card i.e. network events
Get the data quota of a SIM
Get the SMS quota of a SIM
Trigger a connectivity reset for a given SIM Card. The actual reset will be done asynchronously. A positive-response only means that the connectivity-reset has been successfully placed into the queue.
Get the list of SMS sent and received by this SIM Card
Submit SMS to specific SIM Card
Get details about the SMS
Cancel SMS that is buffered for SIM Card and not yet delivered
Top up the data volume of a specific SIM Card
Get the daily usage generated by a SIM Card
Top up the data volume of specific SIM Cards
You get a detailed description of how to use each request by clicking on the specific request bar. To unfold an overview of the specific instructions and parameters you need to click on the button “Try it out”.
The usage of 1NCE REST API via the customer’s external system demands for an authentication first. Therefore, the authentication via OAuth2 with the same credentials being used as for the 1NCE Customer Portal (e-mail address and password) is required. As an “API User” the authentication method with client_id and client_secret is required.
The OAuth2 authentication is necessary to get a token with credentials of the 1NCE Customer Portal with the following workflow:
The UUID for authentication has a validity period of 240 minutes. Notice: If the 240 minutes have expired the authentication process needs to be repeated. Send the authentication request via POST to
‘authorization’: ‘Basic <base64 encoded username:password>’
“access_token”:”6ba7b810-9dad-11d1-80b4-00c04fd43XXX”, // this is the
UUID token you want to use for authentication
“appToken”:”<application_token>”, // not relevant in this context
“orgId”:4321 // example
Note: Only when you are authenticated you can send requests and receive the responses.
1NCE also offers a comfortable overview of all API requests in an API doc which you can access with link
at the top of the page.
(This page might not be fully functional with every browser, prefered: Firefox 63.0 or higher)