1NCE API
Community OpenAPI document · agent-readyIOTDevice Managementoauth225 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage 1NCE IoT SIM connectivity: activate and configure SIM cards, top up data, send and receive SMS, and check quota, usage, and connectivity status by ICCID. Authenticates with OAuth2 client credentials.
Use for: Activate a new IoT SIM card for a deployed device, Top up the data volume on a SIM before it runs out, Check the remaining data quota for a SIM by its ICCID, Send an SMS command to a device over its SIM
Not supported: Does not handle device firmware, hardware provisioning, or non-cellular connectivity like WiFi or Bluetooth. Use for 1NCE cellular SIM connectivity management only.
The 1NCE API manages cellular connectivity for IoT devices, letting you activate and configure SIM cards, top up their data volume, send and receive SMS, and track quota, usage, and network events by ICCID. It also exposes connectivity orders, available products, and support service requests, all authenticated with OAuth2 client credentials. Built for machine-to-machine deployments, it identifies each SIM by its ICCID and returns status, location, and diagnostic information for remote fleets.
Install Jentic One Beta
Connect the 1NCE API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 1NCE API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2F1nceapi%2Fmain" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2F1nceapi%2Fmain" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with 1NCE API.
Activate, deactivate, label, and IMEI-lock SIM cards for IoT devices
Top up the data volume of individual SIMs or batches of SIMs
Retrieve a SIM's data quota, SMS quota, daily usage, and connectivity status
Send SMS to a SIM, list received messages, and cancel undelivered ones
Look up connectivity information and events for a SIM by ICCID
Place and track connectivity orders and open support service requests
Transfer SIMs between customers and configure automatic top-ups
Use Cases
Patterns agents use 1NCE API for, with concrete tasks.
★ Agent-Managed IoT Connectivity
An AI agent monitors a fleet of 1NCE SIMs, tops up a SIM's data before it runs dry, and toggles activation as devices are deployed or retired, without an operator opening the 1NCE portal. Through Jentic the agent discovers the SIM, quota, and top-up operations by intent and calls them with stored OAuth2 credentials.
Check the data quota for a SIM by its ICCID and top up its data volume if the remaining quota is low
SIM Lifecycle Automation
Device manufacturers activate SIMs at the point of shipment, label them to match asset records, apply an IMEI lock to bind a SIM to its hardware, and deactivate SIMs when devices are decommissioned. Status and event history for each SIM are available by ICCID for auditing.
Activate a SIM identified by its ICCID, set a label matching the device serial number, and apply an IMEI lock
Device SMS and Diagnostics
IoT platforms send SMS commands to remote devices, read the SMS a device has sent back, and cancel messages still buffered for delivery. Network event history and connectivity information help diagnose why a device has dropped off the network.
Submit an SMS to a device by its ICCID, then list the SMS sent and received by that SIM to confirm delivery
Key Endpoints
25 endpoints — the 1nce api manages cellular connectivity for iot devices, letting you activate and configure sim cards, top up their data volume, send and receive sms, and track quota, usage, and network events by iccid.
METHOD
PATH
DESCRIPTION
GET
/v1/sims
List SIMs
GET
/v1/sims/{iccid}
Get status information for a SIM
PUT
/v1/sims/{iccid}
Update a SIM (activate, deactivate, label, IMEI lock)
POST
/v1/sims/topup
Top up the data volume of SIMs
GET
/v1/sims/{iccid}/quota/data
Get a SIM's data quota
POST
/v1/sims/{iccid}/sms
Submit an SMS to a SIM
GET
/v1/orders
List orders
GET
/v1/products
List products
GET
/v1/sims
List SIMs
GET
/v1/sims/{iccid}
Get status information for a SIM
PUT
/v1/sims/{iccid}
Update a SIM (activate, deactivate, label, IMEI lock)
POST
/v1/sims/topup
Top up the data volume of SIMs
GET
/v1/sims/{iccid}/quota/data
Get a SIM's data quota
POST
/v1/sims/{iccid}/sms
Submit an SMS to a SIM
GET
/v1/orders
List orders
GET
/v1/products
List products
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the 1NCE API by hand means running the OAuth2 client-credentials flow against its token endpoint, refreshing tokens, and tracking SIMs by ICCID yourself. Through Jentic you install once, import 1NCE from the API Directory, store the credential once, and your agent calls it.
Permission scoping
1NCE identifies SIMs by ICCID in the URL path (/v1/sims/{iccid} and its sub-resources), so a rule can pin your agent to the operations for one SIM. You choose the operations it may call, so destructive ones like SIM deactivation or transfer are not included unless you add them.
Credential isolation
Your 1NCE OAuth2 credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'top up a SIM' or 'check SIM data quota', and Jentic returns the matching 1NCE operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using 1NCE API through Jentic.
What authentication does the 1NCE API use?
The 1NCE API authenticates with OAuth2 using the client-credentials flow per its OpenAPI spec: your agent exchanges a client id and secret for a bearer token at the token endpoint, then sends that token on each request. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.
Can I top up a SIM's data volume with the 1NCE API?
Yes. One operation tops up the data volume for a batch of SIMs and another tops up a single SIM identified by its ICCID, so an agent can add data to a device that is about to run out. You can also read a SIM's remaining data quota first to decide whether a top-up is needed.
Can I limit what my agent is allowed to do with 1NCE?
Yes. Write a rule that allows only the SIM read and top-up operations for one ICCID, so your agent can check quota and add data for that device and touch nothing else, and every call it makes is logged.
What are the rate limits for the 1NCE API?
The OpenAPI spec does not specify rate limits. Check the 1NCE documentation at https://1nce.com for current limits before running an agent at high volume against the SIM and SMS endpoints.
How do I top up a SIM through Jentic?
Search Jentic for the intent 'top up a SIM', which returns the top-up operation and its input schema; the agent then submits the ICCID and the data volume to add. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a 1NCE MCP server?
You don't need an MCP server to give your agent the 1NCE API. Jentic connects it directly from the API Directory: import it, store your OAuth2 credential once, and your agent calls the SIM, quota, and SMS operations. Because operations are discovered on demand, no extra tool definitions are loaded into the agent's context.
GET STARTED