canonical: https://jentic.com/apis/emnify.net

# EMnify APIs

EMnify is a cellular IoT connectivity platform. Its APIs manage SIMs, endpoints, users, organizations, tariff plans, and integrations across global mobile networks. Jentic publishes and maintains the OpenAPI specifications for both EMnify surfaces, so AI agents can authenticate, provision connectivity, send SMS, set data quotas, and administer multi-tenant workspaces through structured tooling. The two APIs share one bearer credential and one control plane, differing only in depth: a compact core surface for essential SIM and endpoint work, and a full enterprise surface for fleet-scale operations.

## For AI agents

An agent can authenticate to EMnify, provision and update SIMs and endpoints, send SMS to IoT devices, set data quotas and traffic limits, read usage and tariff data, and administer users and workspaces across both the core and enterprise APIs.

## Scope

Use for: Managing cellular IoT connectivity through EMnify: SIM and endpoint lifecycle, SMS to devices, data quotas, tariff plans, users, and event integrations.

Not supported:
- device firmware
- device cloud
- MQTT data brokering
- non-cellular networks
- hardware provisioning

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| EMnify Enterprise API | iot | 181 | Operate the full EMnify cellular IoT control plane - endpoints, SIMs, users, organizations, tariff plans, and integrations across 181 endpoints. |
| EMnify API | iot | 13 | Authenticate, manage SIM and endpoint lifecycle, send SMS, and read service profiles on EMnify's cellular IoT platform. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Basic SIM, endpoint, and SMS operations | emnify | The core API covers authentication, SIM and endpoint lifecycle, SMS, and tariff reads in 13 endpoints without the full administrative surface. |
| Fleet-scale operations and administration | emnify-api | The enterprise API adds bulk endpoint calls, data quotas, traffic limit extensions, MFA user management, workspaces, and event integrations across 181 endpoints. |
| Send SMS to a managed IoT endpoint | emnify | Both APIs expose SMS, but the core API is the leaner path when only sending is needed. |
| Set a data quota or cost cap on an endpoint | emnify-api | Data quotas and traffic limit extensions exist only on the enterprise surface. |

## Cross-API use cases

### Provision then scale a device fleet

Start a new deployment on the core API by authenticating, creating SIMs, binding endpoints, and sending a provisioning SMS, then move fleet-wide administration to the enterprise API for bulk endpoint updates, data quotas, and event integrations as the fleet grows. One bearer token spans both surfaces.

Example prompt: Use emnify to POST /authenticate, POST /sim, and POST /endpoint for the initial devices, then use emnify-api to POST /api/v2/endpoint/multi for batch updates and POST /api/v1/endpoint/{endpoint_id}/quota/data to cap costs.

### Send SMS and enforce cost controls

Deliver a command SMS to a managed endpoint through the core API, then apply a data quota and read daily usage statistics on the enterprise API so a runaway device cannot generate a surprise bill. Cost controls live on the enterprise surface while the SMS command channel is available on both.

Example prompt: Use emnify to POST /sms to the endpoint, then use emnify-api to GET /api/v1/endpoint/{endpoint_id}/stats/daily and POST /api/v1/endpoint/{endpoint_id}/quota/data to set a hard cap.

### Reconcile tariffs across both surfaces

Read service profiles and tariff plans on the core API to reconcile fleet billing, then use the enterprise API to adjust workspace and organization configuration or invite the finance user who owns the reconciliation. This keeps plan assignment and account administration consistent across a multi-tenant setup.

Example prompt: Use emnify to GET /service_profile and GET /tariff_plan for the reconciliation report, then use emnify-api to POST /api/v2/user/invitation to add the finance owner.

## Why Jentic

- **Setup:** Wiring EMnify by hand means exchanging credentials for a bearer token, threading it through two API surfaces and their control-plane operations, and building your own retries against cdn.emnify.net. With Jentic you install once, add the EMnify APIs from the Jentic directory, store the token once, and your agent calls both surfaces.
- **Permission scoping:** EMnify puts the SIM id and endpoint id in the URL path, so your own rules can pin an agent to one SIM or one endpoint and to a chosen set of operations. Actions like creating SIMs, sending SMS, or setting data quotas are not available to the agent unless you add them.
- **Credential handling:** 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, and the same token serves both the core and enterprise APIs.
- **Discovery method:** Agents search the Jentic directory by intent such as 'provision a new IoT SIM' or 'set an endpoint data quota', and Jentic returns the matching EMnify operation with its input schema, so the agent picks the right surface and endpoint without browsing reference docs.

## Related vendors

- **Particle** — Integrated IoT device cloud with bundled connectivity and firmware management, where EMnify is connectivity-only.
- **Twilio** — Programmable SMS and IoT SIM connectivity, useful for reaching phones outside a managed EMnify fleet.
- **Hologram** — Global cellular IoT SIM and connectivity management, an adjacent alternative for device fleets.

## FAQ

### What is the difference between the two EMnify APIs?

The core EMnify API is a compact 13-endpoint surface for authentication, SIM and endpoint lifecycle, SMS, and tariff reads. The enterprise EMnify API is a 181-endpoint surface that adds bulk endpoint operations, data quotas, traffic limit extensions, MFA-protected user management, organization and workspace configuration, and event integrations. Start on the core API and move to the enterprise API when a deployment needs fleet-scale control.

### Do both EMnify APIs share the same credentials?

Yes. Both surfaces use HTTP Bearer authentication, and a token obtained from EMnify's authenticate endpoint works against both the core and enterprise APIs. You store the token once and use it across all EMnify operations.

### Why does Jentic publish OpenAPI specs for EMnify?

EMnify does not publish a stable OpenAPI specification at these entry points. Jentic generates and maintains both specs and validates them against the live API so that AI agents and developers can call EMnify through structured tooling rather than hand-built clients.

### Can an agent manage a full IoT fleet through these APIs?

Yes. An agent can provision SIMs and endpoints, send SMS to devices, apply data quotas and traffic limits, read usage and cost statistics, administer users and workspaces, and configure event integrations. The core API covers day-to-day SIM and endpoint work while the enterprise API handles bulk and multi-tenant operations.

### Does EMnify handle device firmware or a device cloud?

No. EMnify is a connectivity-only platform focused on cellular SIMs, endpoints, SMS, and the associated account controls. It does not manage device firmware, provide a device cloud, or broker MQTT data. Teams that also need firmware or a device cloud typically pair EMnify with a platform such as Particle.

### What happens when an EMnify API returns a rate limit response?

The OpenAPI specs do not declare quantitative rate limits, and EMnify enforces limits at the account level. Treat HTTP 429 responses as authoritative and back off using the Retry-After header when it is present, on both the core and enterprise surfaces.