EMnify Enterprise API

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

★ Only Publicly Available OpenAPI DocumentIOTDevice Managementbearer181 EndpointsREST

Install Jentic One Beta

Connect the EMnify Enterprise API to your agent

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

Step 1: 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

Step 2: 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 Enterprise API.

Manage endpoint lifecycle in bulk including create, update, and delete operations on the multi-endpoint resource

Configure traffic limit extensions, data quotas, and operator blacklists at the endpoint level

Read endpoint usage and cost statistics including daily breakdowns

GET STARTED

Start building with EMnify Enterprise API

Explore with Jentic

View OpenAPI Document

For Agents

Operate the full EMnify cellular IoT control plane - endpoints, SIMs, users, organizations, tariff plans, and integrations across 181 endpoints.

Use for: I need to bulk update endpoints in our IoT fleet, Get the daily usage statistics for an endpoint, Send an SMS to a specific IoT endpoint, Set a data quota on an endpoint to cap costs

Not supported: Does not handle device firmware, MQTT data brokering, or non-cellular networks - use for cellular IoT control plane operations only.

Jentic publishes the only available OpenAPI specification for EMnify Enterprise API, keeping it validated and agent-ready. The Enterprise API is EMnify's full administrative surface for IoT connectivity - endpoint and SIM lifecycle, MFA-protected user management, organization and workspace configuration, tariff and service profiles, integrations, and event streams. With 181 endpoints across 19 functional areas, it covers everything from a single SIM update to full multi-tenant fleet operations. Use it when a deployment needs deep platform control rather than the minimal core feature set.

Use Cases

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

★ Large-Scale Endpoint Operations

Manage tens of thousands of IoT endpoints with bulk create, update, and delete calls rather than per-endpoint loops. The Enterprise API exposes POST, PATCH, and DELETE on /api/v2/endpoint/multi specifically for batch operations, alongside per-endpoint controls for connectivity, quotas, and SMS. Operations teams use this to keep large fleets in sync with the device-of-record system.

POST /api/v2/endpoint/multi with the array of endpoint records, then PATCH /api/v2/endpoint/multi to apply state changes in batches.

Cost Control via Quotas and Limits

Cap data usage and apply traffic limit extensions on individual endpoints to control costs across a fleet. The API supports setting and removing data quotas, listing active extensions, and reading usage statistics so finance can model and constrain monthly spend. Engineering teams wire these into anomaly detection so a runaway device cannot generate a surprise bill.

Call GET /api/v1/endpoint/{endpoint_id}/stats/daily to read usage, then POST /api/v1/endpoint/{endpoint_id}/quota/data to set a hard data cap.

Multi-Tenant Workspace Administration

Provision users, manage organizations, and configure workspaces for multi-tenant IoT product builds where customer accounts need their own isolated EMnify state. The API supports user invitation, MFA enrolment, password management, and organization/workspace operations. Platform teams use this to expose self-service connectivity provisioning to their own customers.

POST /api/v2/user/invitation to invite the new admin and POST /api/v1/user/mfa to set up MFA for the account.

Event Integrations and Webhooks

Configure integrations and application tokens so downstream systems can subscribe to events from the EMnify platform - endpoint state changes, SMS receipts, and connectivity events. The integrations and events resources expose the configuration surface needed to wire EMnify into a data pipeline. Engineering teams use this to drive real-time alerting on connectivity degradation.

Configure an integration via the integrations resource and validate by reading endpoint events via GET /api/v1/endpoint/{endpoint_id}/event.

Agent-Driven Fleet Triage

An operations agent receives an alert about a stuck device, queries connectivity info, resets the connectivity, and posts a status SMS - all without a human dashboard session. Through Jentic the agent searches by intent, loads the schemas, and chains the calls. Triage that previously required a multi-screen dashboard navigation completes as a single agent task.

Search Jentic for 'reset endpoint connectivity', execute GET /api/v1/endpoint/{endpoint_id}/connectivity, PATCH /api/v1/endpoint/{endpoint_id}/connectivity, and POST /api/v1/endpoint/{endpoint_id}/sms in sequence.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/api/v1/authenticate

Retrieve an authentication token

POST

/api/v2/endpoint/multi

Bulk create endpoints

PATCH

/api/v2/endpoint/multi

Bulk update endpoints

GET

/api/v1/endpoint/{endpoint_id}/stats/daily

Daily usage statistics for an endpoint

POST

/api/v1/endpoint/{endpoint_id}/sms

Send SMS to an endpoint

POST

/api/v1/endpoint/{endpoint_id}/quota/data

Set a data quota on an endpoint

PATCH

/api/v1/endpoint/{endpoint_id}/connectivity

Reset endpoint connectivity

POST

/api/v2/user/invitation

Invite a user to the workspace

POST

/api/v1/authenticate

Retrieve an authentication token

POST

/api/v2/endpoint/multi

Bulk create endpoints

PATCH

/api/v2/endpoint/multi

Bulk update endpoints

GET

/api/v1/endpoint/{endpoint_id}/stats/daily

Daily usage statistics for an endpoint

POST

/api/v1/endpoint/{endpoint_id}/sms

Send SMS to an endpoint

Why Jentic?

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

Credential isolation

Your EMnify token 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 'send an SMS to a cellular endpoint' or 'read an endpoint's daily usage', and Jentic returns the matching EMnify operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using EMnify Enterprise API through Jentic.

Why is there no official OpenAPI spec for EMnify Enterprise 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 Enterprise API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the EMnify Enterprise API use?

The API uses HTTP Bearer authentication. Call POST /api/v1/authenticate with credentials to obtain a token, then send it in the Authorization header. Through Jentic, credentials are stored encrypted in the vault and the bearer is injected at execution time.

Can I bulk update IoT endpoints with the EMnify Enterprise API?

Yes. POST, PATCH, and DELETE on /api/v2/endpoint/multi accept arrays of endpoint records for batch operations, which is the recommended path for fleet-scale changes.

How do I set a data quota on an endpoint through Jentic?

Search Jentic for 'set IoT endpoint data quota', load the schema for POST /api/v1/endpoint/{endpoint_id}/quota/data, and execute it. Use GET on the same path to confirm the active quota.

What are the rate limits for the EMnify Enterprise 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 reset connectivity on a stuck endpoint?

Yes. PATCH /api/v1/endpoint/{endpoint_id}/connectivity triggers a connectivity reset, and GET on the same path returns the current connectivity state for inspection.

Can I limit what my agent is allowed to do with the EMnify Enterprise API?

Yes. Because you run Jentic One yourself, your own rules decide which of the 181 operations and which credentials the agent may use. Since the endpoint id sits in the URL path (/api/v1/endpoint/{endpoint_id}/...), you can pin the agent to a single cellular endpoint and allow only, say, reading its daily stats via GET /api/v1/endpoint/{endpoint_id}/stats/daily and sending SMS via POST /api/v1/endpoint/{endpoint_id}/sms. Operations you do not grant, such as PATCH /api/v1/endpoint/{endpoint_id}/connectivity or POST /api/v1/endpoint/{endpoint_id}/quota/data, stay off limits, and your token is injected at execution time without ever entering the agent's prompt or logs.

EMnify Enterprise API

Connect the EMnify Enterprise API to your agent

Capabilities

Start building with EMnify Enterprise API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs