1NCE API

Name: 1NCE API API
Brand: 1NCE API
Availability: InStock

★ Only Publicly Available SpecIOTDevice Managementoauth225 EndpointsREST

For Agents

Manage cellular IoT SIM cards on the 1NCE network: activate, label, top up, send SMS, and inspect connectivity status for connected devices.

Quickstart

Get started with 1NCE API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"manage a 1NCE IoT SIM card"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with 1NCE API API.

Activate, deactivate, and relabel SIM cards in bulk or individually by ICCID

Top up data volume on a single SIM or across a list of SIMs in one call

Send SMS to a deployed SIM and cancel queued SMS that have not yet been delivered

Read connectivity diagnostics, location, and network event history for a specific SIM

GET STARTED

Start building with 1NCE API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for 1NCE API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for 1NCE API, keeping it validated and agent-ready. The 1NCE API gives developers programmatic control over cellular IoT connectivity, including activating SIMs, querying data and SMS quotas, sending SMS to devices, and triggering connectivity resets across a global cellular network. It exposes 25 endpoints covering SIM lifecycle management, order placement for new SIM cards, product catalog access, usage reporting, and support service requests. The API is designed for fleet operators running embedded devices, asset trackers, and industrial sensors that need lightweight cellular data plans with predictable pricing.

Use Cases

Patterns agents use 1NCE API API for, with concrete tasks.

★ IoT Fleet SIM Lifecycle Management

Operators of cellular IoT fleets use the 1NCE API to activate new SIMs as devices ship, deactivate SIMs returned from the field, and relabel them as devices are reassigned. The PUT /v1/sims/{iccid} and POST /v1/sims endpoints handle individual and bulk state changes so a backend can mirror SIM status against its device inventory without manual portal work. This typically replaces a spreadsheet-driven workflow with a few hours of integration work.

Activate the SIM with ICCID 8988228066612345678 and set its label to 'tracker-fleet-A'

Remote Device Connectivity Recovery

When a deployed sensor or asset tracker stops reporting, an operations agent can call GET /v1/sims/{iccid}/connectivity_info and GET /v1/sims/{iccid}/events to diagnose the failure, then POST /v1/sims/{iccid}/reset to force a fresh network attachment. This avoids dispatching a field technician for problems that are recoverable over the air and shortens incident resolution from hours to minutes.

Pull connectivity info and recent events for ICCID 8988228066612345678, then trigger a connectivity reset if the SIM has been detached for more than two hours

Data and SMS Quota Monitoring

Fleet billing teams call GET /v1/sims/{iccid}/quota/data and /quota/sms alongside GET /v1/sims/{iccid}/usage to track consumption against monthly allowances. Combined with POST /v1/sims/topup or POST /v1/sims/{iccid}/topup, this powers automated low-balance handling so devices never silently exhaust their cellular budget. Useful for any deployment where data overruns translate directly into incident response cost.

Get the remaining data quota for ICCID 8988228066612345678 and top it up by 500MB if less than 50MB remains

Device-to-Cloud SMS Command Dispatch

Some IoT devices use SMS as an out-of-band control channel for configuration updates or wakeups. The POST /v1/sims/{iccid}/sms endpoint submits an SMS to a specific SIM, and GET /v1/sims/{iccid}/sms returns delivery history for audit. Pairing this with DELETE /v1/sims/{iccid}/sms/{id} lets operators cancel queued commands when device state changes mid-flight.

Send the SMS payload 'REBOOT' to the SIM with ICCID 8988228066612345678 and confirm the message reached delivered status

AI Agent IoT Operations Assistant

An AI agent integrated with Jentic can act as a tier-1 IoT operations responder: when a device alert fires, the agent searches Jentic for the 1NCE SIM operation, loads the schema, and executes connectivity diagnosis, quota top-up, or SIM reset without a human in the loop. This collapses common runbooks into single agent invocations and frees on-call engineers for genuine incidents. Through Jentic the OAuth2 client credentials are vaulted, so the agent never sees the raw 1NCE API key.

Search Jentic for 'manage 1NCE SIM card', load the SIM topup operation, and execute a 250MB top-up for ICCID 8988228066612345678

Key Endpoints

25 endpoints — jentic publishes the only available openapi specification for 1nce api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v1/sims

List all SIMs with status and labels

PUT

/v1/sims/{iccid}

Modify a SIM to activate, deactivate, relabel, or change IMEI lock

POST

/v1/sims/{iccid}/topup

Top up the data volume on a single SIM

POST

/v1/sims/{iccid}/reset

Trigger a connectivity reset for a SIM

GET

/v1/sims/{iccid}/usage

Get daily usage generated by a SIM

POST

/v1/sims/{iccid}/sms

Submit an SMS to a specific SIM

GET

/v1/sims/{iccid}/connectivity_info

Retrieve connectivity and location info for a SIM

POST

/v1/orders

Place a new SIM order

GET

/v1/sims

List all SIMs with status and labels

PUT

/v1/sims/{iccid}

Modify a SIM to activate, deactivate, relabel, or change IMEI lock

POST

/v1/sims/{iccid}/topup

Top up the data volume on a single SIM

POST

/v1/sims/{iccid}/reset

Trigger a connectivity reset for a SIM

GET

/v1/sims/{iccid}/usage

Get daily usage generated by a SIM

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

1NCE OAuth 2.0 client credentials are stored encrypted in the Jentic vault (MAXsystem). Jentic exchanges them for a short-lived access token at /management-api/oauth/token and injects only the scoped bearer token into the request — the agent never sees the raw client secret.

Intent-based discovery

Agents search Jentic by intent (e.g., 'top up an IoT SIM' or 'reset 1NCE SIM connectivity') and Jentic returns the matching 1NCE operation with its full input schema, so the agent calls the right endpoint without browsing 1NCE documentation.

Time to first call

Direct 1NCE integration: 1-3 days for OAuth handling, ICCID lookups, and async reset polling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio Super SIM

Twilio's global IoT SIM platform with multi-network roaming and a similar SIM-by-ICCID management model.

Choose Twilio Super SIM when the fleet is already on Twilio's stack or needs Twilio's broader programmable connectivity ecosystem. Choose 1NCE for flat-rate, lifetime data plans aimed at low-bandwidth IoT.

Alternative

Twilio Wireless

Twilio's earlier IoT SIM API focused on US/EU coverage and per-MB billing.

Pick Twilio Wireless for North America-centric deployments where per-MB pricing fits the usage profile. Pick 1NCE for predictable lifetime data bundles and European-led coverage.

Complementary

Particle Device Cloud

Device-side cloud for firmware OTA, function calls, and event streams that pairs with 1NCE-managed cellular connectivity.

Use Particle alongside 1NCE when devices need application-layer features like OTA firmware and remote function calls in addition to the underlying cellular link 1NCE provides.

FAQs

Specific to using 1NCE API API through Jentic.

Why is there no official OpenAPI spec for 1NCE API?

1NCE GmbH does not publish an OpenAPI specification on its developer site. Jentic generates and maintains this spec so that AI agents and developers can call the 1NCE API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the 1NCE API use?

The 1NCE API uses OAuth 2.0 with the client credentials flow. You exchange a client ID and secret at /management-api/oauth/token for a bearer access token, then send that token in the Authorization header on every call. Through Jentic the OAuth credentials are stored encrypted in the vault and the agent only ever sees a scoped access token.

Can I top up SIM data programmatically with the 1NCE API?

Yes. POST /v1/sims/{iccid}/topup tops up a single SIM by ICCID, and POST /v1/sims/topup tops up a list of SIMs in one call. You can also configure auto top-up via POST /v1/sims/autoTopup so SIMs replenish without manual intervention.

What are the rate limits for the 1NCE API?

The 1NCE OpenAPI specification does not publish explicit rate limits. 1NCE applies fair-use throttling on the management API and recommends batching SIM operations through the bulk POST /v1/sims endpoint rather than calling per-SIM endpoints in a tight loop. If you hit a 429 response, back off and retry with exponential delay.

How do I reset a stuck SIM through Jentic?

Search Jentic for 'reset 1NCE SIM connectivity', load the POST /v1/sims/{iccid}/reset operation, then execute it with the target ICCID. The reset is queued asynchronously, so follow up with GET /v1/sims/{iccid}/status to confirm the SIM has reattached. Install with pip install jentic and use the async search, load, execute pattern.

Can the 1NCE API send SMS to deployed devices?

Yes. POST /v1/sims/{iccid}/sms submits an SMS to the SIM identified by ICCID, GET /v1/sims/{iccid}/sms lists the SMS history for that SIM, and DELETE /v1/sims/{iccid}/sms/{id} cancels a queued SMS that has not yet been delivered. This is intended for low-volume command and control SMS to IoT devices, not consumer messaging.

Can I place SIM orders through the API?

Yes. POST /v1/orders submits a new order against the products returned by GET /v1/products, and GET /v1/orders/{order_number} fetches the status of a specific order. This lets procurement systems trigger SIM card shipments without using the 1NCE web portal.