EMnify API

Name: EMnify API API
Brand: EMnify API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIOTDevice Managementbearer13 EndpointsREST

For Agents

Authenticate, manage SIM and endpoint lifecycle, send SMS, and read service profiles on EMnify's cellular IoT platform.

Connect the EMnify API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EMnify 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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 EMnify API API.

Authenticate against EMnify and obtain a bearer token for subsequent calls

Create, list, update, and delete SIMs to manage the cellular IoT fleet

Provision and update endpoints that bind SIMs to IoT devices

Send SMS to a managed endpoint over the EMnify network

GET STARTED

Start building with EMnify API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for EMnify API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for EMnify API, keeping it validated and agent-ready. EMnify is a cellular IoT connectivity platform for managing SIMs, endpoints, and SMS across global networks. This compact API exposes the core operations needed to authenticate, manage SIM lifecycle, configure endpoints, send SMS, and read service profiles and tariff plans. Use it for IoT fleet operations and integrations that need only the essential SIM and endpoint controls without the full Enterprise surface.

Use Cases

Patterns agents use EMnify API API for, with concrete tasks.

★ IoT Fleet SIM Provisioning

Provision and manage SIMs in EMnify as part of a device manufacturing or activation flow rather than clicking through the dashboard. The API supports list, create, update, and delete operations on SIMs and endpoints, enabling fleets of thousands of devices to be brought online from automation. Operations teams use this to keep SIM state in sync with the device manufacturing system of record.

POST /sim with the SIM identifier and service profile, then POST /endpoint to bind the SIM to a device record.

SMS Command Channel

Send SMS to managed IoT endpoints to deliver commands or trigger actions on devices that prefer SMS over data. The API exposes POST /sms for sending and the endpoint resource for managing the destination. Engineering teams use this for low-power devices and as a fallback channel when data connectivity is unavailable.

POST /sms with the endpoint identifier and message body to deliver a command to the device.

Service Profile and Tariff Reconciliation

Read service profiles and tariff plans periodically to reconcile billing assumptions and confirm that fleet SIMs are on the right plan. The API exposes GET /service_profile and GET /tariff_plan for inventory listing. Finance and operations teams use this to spot mis-assigned SIMs before invoices are generated.

Call GET /service_profile and GET /tariff_plan and produce a reconciliation report against the local SIM-to-plan mapping.

Agent-Driven SIM Onboarding

An agent in a device manufacturing flow takes a new device record, creates the SIM and endpoint in EMnify, sends a provisioning SMS, and writes back the resulting connectivity status. Through Jentic the agent searches by intent, loads the schemas, and executes the calls without bespoke client code. Onboarding a new device drops from a multi-step manual process to a single agent task.

Search Jentic for 'provision a new IoT SIM', execute POST /authenticate, POST /sim, POST /endpoint, and POST /sms in sequence, and return the connectivity verdict.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/authenticate

Authenticate and obtain a bearer token

GET

/sim

List SIMs in the fleet

POST

/sim

Create a new SIM

PATCH

/sim/{sim_id}

Update a SIM

GET

/endpoint

List endpoints

POST

/endpoint

Create an endpoint

POST

/sms

Send an SMS to an endpoint

GET

/service_profile

List service profiles

POST

/authenticate

Authenticate and obtain a bearer token

GET

/sim

List SIMs in the fleet

POST

/sim

Create a new SIM

PATCH

/sim/{sim_id}

Update a SIM

GET

/endpoint

List endpoints

POST

/endpoint

Why though Jentic?

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

Credential isolation

EMnify credentials are stored encrypted in the Jentic vault. Agents receive scoped access tokens — the raw application token never enters the agent's context, and Jentic handles the POST /authenticate exchange.

Intent-based discovery

Agents search by intent (e.g., 'provision a new IoT SIM') and Jentic returns matching EMnify operations with their input schemas, so the agent calls the right endpoint without reading docs.

Time to first call

Direct EMnify integration: 1-2 days for auth handling, SIM lifecycle, and SMS plumbing. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

EMnify Enterprise API

Larger enterprise surface from the same vendor with 180+ endpoints

Use the Enterprise API when the use case needs deep features like trusted devices, traffic limit extensions, or quotas; this core API is the leaner choice.

Alternative

Particle Device Cloud API

Device cloud platform with built-in connectivity for IoT

Choose Particle when the team needs an integrated device cloud and firmware platform; choose EMnify when only cellular connectivity is required.

Complementary

Twilio API

Pair with Twilio for non-cellular SMS delivery to operators

Use Twilio when SMS needs to flow to phones outside the IoT fleet; EMnify SMS is for managed endpoints.

FAQs

Specific to using EMnify API API through Jentic.

Why is there no official OpenAPI spec for EMnify API?

EMnify does not publish a stable OpenAPI specification at this entry point. Jentic generates and maintains this spec so that AI agents and developers can call EMnify 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 EMnify API use?

The API uses HTTP Bearer authentication. Call POST /authenticate to obtain a token, then send it in the Authorization header on subsequent requests. Through Jentic, the credentials are stored encrypted in the vault and the token is injected automatically.

Can I send SMS to an IoT device with the EMnify API?

Yes. POST /sms accepts an endpoint identifier and message body and queues the SMS for delivery over the EMnify network.

How do I provision a new SIM through Jentic?

Search Jentic for 'provision a new IoT SIM', load the schema for POST /sim, and execute it. Follow with POST /endpoint to bind the SIM to a device record.

What are the rate limits for the EMnify API?

The OpenAPI spec does not declare quantitative rate limits; EMnify enforces limits at the account level. Treat HTTP 429 responses as authoritative and back off using the Retry-After header when present.

Can I list available tariff plans before assigning one?

Yes. GET /tariff_plan returns the tariff plans available to the account, and GET /service_profile returns the matching service profiles, so the right plan can be selected before SIM creation.