English 
Dutch 
German 
Spanish - Global Presence
- Fully Managed Solutions
- Wholesale Pricing
- Over 20 years of expertise
Enterprise eSIM MDM Integration: connect provisioning to the stack you already run
If you manage hundreds or thousands of corporate devices through Jamf, Microsoft Intune or VMware Workspace ONE, you already know where the process breaks down. Your MDM platform handles configurations, security policies, app distribution, compliance monitoring. But the moment mobile connectivity enters the picture, the automation stops. SIM cards get ordered, shipped, manually activated. Or employees receive a QR code in a standalone email that goes out completely outside your MDM workflow.
Enterprise eSIM MDM integration closes that gap. Not by replacing your device management platform, but by exposing eSIM provisioning through an API your existing systems can call. At Weconnect, we build that connection with your IT team. One integration. Whatever MDM you run. Discover our Remote SIM Provisioning Platform
No commitment. We map the integration with your IT team and show you what’s possible.
A passionate team with more than
20 years of expertise in eSIM management for traveling teams.
How the API integration works
Weconnect offers a RESTful API that covers the full eSIM lifecycle from your own systems. The provisioning flow runs in five steps.
eSIM profiles start as blank SIMs, unbound to any end user or subscription. You hold that inventory centrally in the Weconnect platform. When an employee requests a product, or when your IT system fires a trigger, the API automatically creates a product binding and configures the associated subscription. The eSIM profile then gets pushed to the eUICC via the SM-DP+ server.
At that point the end user receives an activation link. That link goes two directions: scan a QR code directly with the device camera, or download the profile via the SM-DP+ server onto the device. From there the eSIM is live.
The critical part for IT teams: that activation link is distributable from your MDM. Intune can carry it inside a configuration profile. Jamf can include it in a Self Service workflow. Workspace ONE can attach it to an onboarding sequence. The API delivers the link. Your MDM distributes it.
API-first instead of a native MDM plugin
Some competitors in this space advertise native partnerships with specific MDM vendors. That sounds appealing until you switch platforms or add a second MDM for a specific department. Then the integration has to be rebuilt from scratch.
Weconnect takes a deliberately MDM-agnostic approach. The RESTful API is platform-independent. SHA256 HMAC-secured webhooks push real-time status updates to any system that can receive them: your MDM, your ITSM platform, a custom orchestration layer you built internally. One integration point, regardless of how many device management platforms your organisation runs.
Running multiple departments on different MDM stacks? The API makes no distinction. Provisioning works identically across all of them. Only the distribution layer differs per team.
Webhook events for IT operations
The Push API sends real-time notifications on every relevant status change. An eSIM profile activates? Webhook. A data session starts or ends? Webhook. An employee crosses a usage threshold? Webhook. You define those events yourself via automation rules in the Weconnect platform, including the threshold values that trigger them.
For IT operations, this means eSIM status lands where you expect it, not in a separate connectivity dashboard, but in your ticketing system, your SIEM, or your own operations tooling.
Billing integration: from provisioning to finance in one flow
The API does not stop at provisioning. Weconnect integrates with payment providers (Stripe, PayPal, Cardknox) and invoicing platforms (Xero, WeFact). That makes it possible to automate the full chain from the moment an employee requests an eSIM to the moment the cost lands on the correct cost centre.
For organisations that allocate connectivity costs per department, project or budget code, this removes the manual reconciliation step between your connectivity platform and your finance system entirely.
Private label distribution
The activation emails your employees receive are fully configurable to your own branding. No Weconnect communication visible to your end users, just your organisation’s look and feel. For IT teams running a standardised onboarding experience, this is a requirement, not a nice-to-have. Link, template, sender address: all configurable.
Where this works best
The combination of API provisioning and MDM distribution performs strongest when scale and speed meet. Onboarding dozens of new employees every month who need international connectivity from day one. A restructuring that moves hundreds of devices between subscriptions without anyone physically touching a SIM card. Seasonal scaling, where you activate a batch of eSIM profiles for a specific period and deactivate them when the work is done.
In each of those scenarios, the API drives provisioning, the MDM handles distribution, and the Weconnect platform manages status and billing from a single point.
Book a technical walkthrough
Want to see exactly how the API connects to your specific MDM environment? Our team walks through the integration with you in a focused technical session. Endpoints, webhook configuration, the provisioning flow that fits your device management setup. No sales pitch involved.
Frequently asked questions
The API is MDM-agnostic. Weconnect delivers the activation link and QR code via the RESTful API. You then distribute that from your MDM of choice, whether that is Jamf Self Service, an Intune configuration profile or a Workspace ONE onboarding flow. The link works in any distribution channel.
A native partnership means the eSIM provider builds a plugin or connector for one specific MDM platform. It works, but it ties you to that platform. Weconnect’s API-first approach is platform-independent: one integration that works regardless of which MDM you run, or how many you have active across your organisation.
All webhook events are signed with SHA256 HMAC. On the receiving end, you can verify that the event genuinely originates from Weconnect and has not been modified in transit.
Yes. Weconnect provides private label email templates. Logo, colours, sender address, template copy: fully configurable. Your employees receive communication that looks like it comes from your organisation.
The platform integrates with Stripe, PayPal and Cardknox for payments, and with Xero and WeFact for invoicing. Automated invoice generation is available as standard.
YOUR GLOBAL NETWORK OPERATOR
Challenge us with your Business SIM problem, you could say we’ve solved some before. Use the contact form, or mail us on info@weconnect.one or call us on +31 20 237 3300.
- Direct response within 1 hour
- Dedicated specialist providing one-on-one guidance
- Obligation free advice
- Fast bespoke offer supplying your exacts company's needs
- NO hidden fees or surprise charges
- Trusted by industry-leading companies worldwide for proven reliability and service quality
Direct response within 1 hour.
How Weconnect helps
businesses like yours move forward
Read how we provide seamless connectivity for leading projects worldwide.
SRT and RIST: What IP Contribution Protocols Need From Your Connection
The speed test at the venue returns 40 Mbps up. The feed is set to 12 Mbps. The engineer has four times the bandwidth the encoder asks for, and the picture still breaks up in bursts that nobody can pin to anything. That gap between a healthy speed test and
5G Standalone and Network Slicing for Broadcast Contribution
An operator offers your production a dedicated slice for the tournament. The proposal describes guaranteed uplink, bounded latency and isolation from the crowd, which is a precise description of every problem a contribution feed has at a full venue. The questions worth asking before signing come next, and they tend
Redundancy and Backup Connectivity for OB Vans and Live Events
Every serious live production has a backup. The transmissions that fail on air are rarely the ones that had no second path. They are the ones where a second path existed and turned out to share something with the first: the same mast, the same operator, the same generator, or
