.png)
Omnissa Workspace ONE UEM Integration Guide
Integrate Workspace ONE UEM with enterprise systems through REST APIs, selected event notifications, bulk operations, and scheduled synchronization workflows.
Omnissa Workspace ONE UEM integration options at a glance
Workspace ONE UEM primarily integrates through REST APIs for Devices, Users, Applications, Profiles, Smart Groups, Compliance Policies, assignments, and device actions. Selected event-notification capabilities can send webhook-style callbacks, while bulk and asynchronous operations support larger administrative workloads. Application packages and endpoint-management artifacts may use file operations that require validation against the target API version. Basic Authentication with the aw-tenant-code header is commonly used, and supported deployments may provide OAuth 2.0. Martini can consume these APIs, receive selected notifications, schedule incremental or reconciliation workflows, transform JSON payloads, and securely manage tenant-specific configuration.
| Integration point | Supported by Omnissa Workspace ONE UEM? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Manage Devices, Users, Applications, Profiles, Smart Groups, Compliance Policies, assignments, inventory, and documented device actions. | Martini can consume the Workspace ONE UEM REST APIs, handle pagination and version-specific paths, transform responses, and orchestrate downstream writes. |
| Webhooks and outbound callbacks | Limited | Receive selected device-management or administrative event notifications where the tenant and event type expose an HTTP callback. | Martini can expose a workflow trigger, validate the notification, retrieve the current UEM object, and process it idempotently. Scheduled polling remains necessary for uncovered events. |
| Bulk and asynchronous operations | Limited | Perform bulk device actions and multi-object administrative operations where documented; completion semantics vary by operation. | Martini can distinguish accepted, completed, partially completed, and failed states, control concurrency, and poll status endpoints where available. |
| File and application package operations | Limited | Upload, download, or manage application packages and endpoint-management artifacts where supported by the API version. | Martini can orchestrate file transfers and metadata calls, but package size, MIME type, upload method, and asynchronous behavior must be configured per API version. |
| Incremental and scheduled synchronization | Yes | Synchronize device, user, application, assignment, and compliance data using filters, pagination, high-water marks, event notifications, and periodic reconciliation. | Martini can schedule workflows, persist synchronization state, apply scoped reconciliation, and route transformed data to enterprise targets. |
| Authentication | Yes | Authenticate with administrator credentials and the aw-tenant-code header; supported deployments may also provide OAuth 2.0. | Martini can store credentials, tenant codes, client secrets, and tokens in environment configuration or secrets management and apply role-aware API calls. |
| SDKs and client libraries | Limited | Omnissa and VMware ecosystems have provided SDKs, but server-side enterprise integrations generally use the Workspace ONE UEM REST APIs. | Martini can consume the documented REST surface directly without requiring a vendor-specific SDK. |
| GraphQL, SOAP, and database access | No | No confirmed public Workspace ONE UEM GraphQL or SOAP surface, and direct database access to the SaaS service is not an appropriate integration method. | Martini should use documented REST APIs, supported event notifications, and supported reporting mechanisms rather than unsupported direct access. |
How Omnissa Workspace ONE UEM exposes data and business events
Workspace ONE UEM REST APIs
REST is the primary Workspace ONE UEM integration surface. It supports administrative and operational functions across Devices, Users, Applications, Profiles, Smart Groups, Compliance Policies, assignments, inventory, and device actions. API paths and operations can vary by tenant release and API version.
Martini implementation pattern
Martini implementation pattern: Martini workflows authenticate to the configured tenant, retrieve or submit resources, handle pagination and version-specific response shapes, map JSON data to canonical models, apply business rules, and write results to downstream systems or expose controlled APIs for callers.
Implementation sequence
Workspace ONE UEM event notifications
Workspace ONE UEM provides event-notification capabilities for selected device-management and administrative events. Coverage is selective and depends on event type, tenant configuration, and version; notifications should not be treated as a complete change stream.
Martini implementation pattern
Martini implementation pattern: a workflow receives the callback, validates and authenticates the request, extracts the relevant identifier, retrieves the current object through the REST API, and performs idempotent downstream processing. Scheduled reconciliation covers events that are not exposed.
Implementation sequence
Workspace ONE UEM bulk and asynchronous operations
Workspace ONE UEM supports bulk administrative operations and APIs that operate on multiple devices or assignments. An accepted request may not mean that processing has completed, and behavior varies by operation.
Martini implementation pattern
Martini implementation pattern: Martini submits bounded bulk requests, records request identifiers where available, distinguishes accepted from completed or failed states, and polls documented status operations with limits before reporting the final outcome.
Implementation sequence
Workspace ONE UEM file and package operations
Application packages and endpoint-management artifacts may support upload, download, assignment, or metadata operations depending on the object and API version. Package size, MIME type, storage, and asynchronous behavior must be confirmed for the target tenant.
Martini implementation pattern
Martini implementation pattern: Martini separates file transport from JSON resource processing, validates package metadata and size, invokes the documented upload or download operation, monitors asynchronous processing where applicable, and records the resulting application or artifact identifier.
Implementation sequence
Common Omnissa Workspace ONE UEM integration patterns
Pattern 1: Synchronize device inventory to ServiceNow
When to use this pattern
Use this pattern when ServiceNow or another operational platform needs current endpoint inventory, ownership, enrollment, and compliance context. A scheduled incremental flow can be supplemented by periodic scoped reconciliation because event coverage is selective.
Integration direction
Example Mapping
| Omnissa Workspace ONE UEM Field | Canonical Field | Target Field |
|---|---|---|
| deviceUuid | sourceDeviceId | uem_device_id |
| serialNumber | serialNumber | serial_number |
| platform | operatingSystem | os |
| enrollmentStatus | enrollmentStatus | enrollment_status |
Martini implementation pattern
A scheduled Martini workflow retrieves paginated Devices using modified-time or status filters where available, persists a high-water mark, normalizes identifiers, enriches ownership and compliance values, and upserts ServiceNow data. It uses bounded concurrency, retries transient responses, and runs periodic reconciliation to detect missed changes or deletions.
Martini capabilities used
- workflows
- scheduled triggers
- API consumption
- pagination handling
- data mapping
- business rules
- error handling
- reusable services
Pattern 2: Provision users and assignments from Workday
When to use this pattern
Use this pattern when worker lifecycle changes should create or update Workspace ONE UEM Users and influence organization-group, Smart Group, application, or profile assignments.
Integration direction
Example Mapping
| Omnissa Workspace ONE UEM Field | Canonical Field | Target Field |
|---|---|---|
| workerId | employeeId | userIdentifier |
| employmentStatus | lifecycleStatus | userStatus |
| department | department | smartGroupRule |
| location | location | organizationGroup |
Martini implementation pattern
Martini receives or retrieves worker changes, resolves stable identifiers, checks whether the Workspace ONE UEM User already exists, applies lifecycle and scope rules, and updates assignments only when the desired state differs. Validation prevents disabled or incomplete workers from triggering unsafe changes, while failures are retried and reported.
Martini capabilities used
- API consumption
- workflow orchestration
- data mapping
- conditional routing
- business rules
- idempotency
- error handling
Pattern 3: Route compliance events to ServiceNow and remediation
When to use this pattern
Use this pattern when compliance changes should create or update incidents and, after appropriate controls, initiate documented Workspace ONE UEM remediation actions.
Integration direction
Example Mapping
| Omnissa Workspace ONE UEM Field | Canonical Field | Target Field |
|---|---|---|
| deviceUuid | deviceId | configuration_item |
| complianceStatus | complianceState | u_compliance_state |
| policyName | policy | short_description |
| lastCheckIn | lastSeen | u_last_check_in |
Martini implementation pattern
A Martini workflow receives a supported notification or polls Compliance Policies and affected Devices, retrieves the current object, deduplicates by device and policy state, and upserts a ServiceNow incident. Approval, authorization, and validation rules can gate any reverse call to a device-action API; transient errors use bounded retries.
Martini capabilities used
- workflow triggers
- API consumption
- data mapping
- deduplication
- authorization
- business rules
- retry handling
- audit logging
Pattern 4: Orchestrate application and profile assignments
When to use this pattern
Use this pattern when department, location, employment status, device ownership, or another authoritative attribute should change Applications or Profiles targeted through Smart Groups.
Integration direction
Example Mapping
| Omnissa Workspace ONE UEM Field | Canonical Field | Target Field |
|---|---|---|
| userId | principalId | assignedUser |
| department | department | smartGroupCriteria |
| applicationId | applicationId | applicationAssignment |
| profileId | profileId | profileAssignment |
Martini implementation pattern
Martini consumes authoritative identity or HR data, evaluates assignment rules, resolves Workspace ONE UEM Smart Groups, and compares desired versus current assignments before applying changes. Bulk operations are used where documented, and asynchronous completion is tracked rather than assumed from an accepted response.
Martini capabilities used
- workflow orchestration
- API consumption
- data mapping
- conditional routing
- bulk request handling
- asynchronous polling
- error handling
Applications commonly integrated with Omnissa Workspace ONE UEM
Workspace ONE UEM can be integrated with adjacent identity, HR, service-management, endpoint, business, and collaboration applications. Martini provides an orchestration layer for API calls, event handling, transformation, safeguards, and reconciliation without requiring a dedicated vendor connector.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| ServiceNow | Synchronize device inventory, ownership, compliance state, and operational incidents with CMDB and IT service-management processes. | Omnissa Workspace ONE UEM → Martini → ServiceNow | Use scheduled or event-triggered workflows to retrieve Devices and compliance information, map identifiers and status values, upsert CMDB data, and create or update incidents. Controlled reverse flows can invoke documented Workspace ONE UEM actions after validation. |
| Microsoft Entra ID | Coordinate workforce identity state, groups, enrollment context, and device information across identity and endpoint-management processes. | Microsoft Entra ID → Martini → Omnissa Workspace ONE UEM | Consume lifecycle or directory data, resolve stable user identifiers, map organization-group and Smart Group rules, and create or update Workspace ONE UEM Users and assignments with idempotent checks. |
| Okta | Synchronize workforce identity and device-management context for access, lifecycle, and endpoint governance processes. | Okta → Martini → Omnissa Workspace ONE UEM | Orchestrate identity changes into Workspace ONE UEM user and assignment updates, or publish selected device state to Okta after retrieving current data from the UEM REST API. |
| Microsoft Intune | Coordinate inventory, application ownership, and migration data during endpoint-management coexistence or migration programs. | Omnissa Workspace ONE UEM → Martini → Microsoft Intune | Extract paginated device and application data from each platform, normalize identifiers and lifecycle states, apply migration rules, and write controlled updates while recording reconciliation results. |
| Salesforce | Associate managed devices and compliance state with users, field-service personnel, or customer-facing operations. | Omnissa Workspace ONE UEM → Martini → Salesforce | Retrieve current Devices and Users, map ownership and compliance attributes to Salesforce objects, and expose a controlled Martini API for selected command requests subject to authorization. |
| Workday | Use worker lifecycle events to create, update, or disable Workspace ONE UEM Users and drive device or application assignment changes. | Workday → Martini → Omnissa Workspace ONE UEM | Receive or retrieve worker changes, resolve the target organization group and Smart Groups, upsert Users, and apply assignment workflows with duplicate protection and auditable outcomes. |
| Jira | Create operational issues from enrollment failures, compliance changes, or device-management exceptions and synchronize resolution status. | Omnissa Workspace ONE UEM → Martini → Jira | Process selected notifications or scheduled compliance queries, map events to Jira issue fields, apply deduplication keys, and optionally invoke documented UEM actions after issue approval. |
| Slack | Publish selected endpoint-management alerts, approvals, or operational summaries to collaboration channels. | Omnissa Workspace ONE UEM → Martini → Slack | Use a Martini workflow to retrieve or receive selected UEM events, apply alert thresholds and redaction, and send concise notifications to approved Slack destinations. |
How to build a Omnissa Workspace ONE UEM integration in Martini
Objective
Establish tenant-specific API access without embedding credentials or tenant codes in workflow logic.
Instructions in Martini
- Store the Workspace ONE UEM base URL, API version, credentials, tenant code, and supported OAuth settings in environment configuration or secrets.
- Confirm administrator role, organization-group scope, API permissions, and the tenant's supported authentication method.
- Configure Martini to consume the documented REST endpoints.
Objective
Select an event-driven, scheduled, or API-led entry point based on the coverage and reliability required.
Instructions in Martini
- Use a workflow trigger for supported Workspace ONE UEM notifications.
- Use a scheduler for incremental synchronization and periodic reconciliation.
- Expose a controlled Martini API when another application must request a UEM operation.
Objective
Obtain complete and current Workspace ONE UEM objects while respecting pagination and tenant-specific behavior.
Instructions in Martini
- Retrieve Devices, Users, Applications, Profiles, Smart Groups, or Compliance Policies through documented REST APIs.
- Follow page and continuation fields and persist a high-water mark where incremental filtering is supported.
- Retrieve the current object after receiving a notification because event payloads may be incomplete.
Objective
Coordinate validation, enrichment, branching, API calls, and downstream writes as a maintainable integration flow.
Instructions in Martini
- Validate required identifiers and organization-group scope.
- Apply conditional routing for lifecycle, compliance, assignment, or remediation scenarios.
- Use reusable workflow logic for common API calls, status checks, and reconciliation operations.
Objective
Convert Workspace ONE UEM JSON into canonical and target-specific structures.
Instructions in Martini
- Map stable identifiers such as device UUIDs, serial numbers, user identifiers, application identifiers, and assignment identifiers.
- Normalize status values, timestamps, nullable fields, nested objects, and enumeration differences.
- Avoid passing arbitrary vendor payloads directly into downstream systems.
Objective
Protect operational processes and ensure that only valid, authorized changes are sent to Workspace ONE UEM or target applications.
Instructions in Martini
- Check whether target objects and assignments already exist before creating them.
- Require authorization, validation, and approval logic for destructive device actions.
- Apply bounded concurrency, severity rules, deduplication, and organization-group constraints.
Common Omnissa Workspace ONE UEM data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Devices | Synchronize endpoint inventory, identifiers, platform, ownership, enrollment, compliance, and last check-in data. | ServiceNow, Microsoft Intune, Salesforce, Jira, asset repositories, analytics platforms | Martini retrieves paginated or incrementally filtered Devices, normalizes identifiers and status values, applies reconciliation rules, and upserts downstream records. |
| Users | Manage enrollment users, ownership relationships, assignments, and device access. | Workday, Microsoft Entra ID, Okta, ServiceNow | Martini uses stable employee or directory identifiers, checks for existing Users, maps organization-group scope, and performs idempotent create or update operations. |
| Applications | Manage internal and public applications, metadata, assignments, and application distribution workflows. | Microsoft Intune, ServiceNow, identity platforms, asset systems | Martini maps application identifiers and lifecycle data, coordinates assignment rules, and handles package operations separately from ordinary JSON calls. |
| Profiles | Configure devices or users with security, connectivity, and operational settings. | ServiceNow, identity systems, compliance reporting platforms | Martini evaluates source attributes and Smart Group rules, then creates or assigns Profiles through documented API operations with validation. |
| Compliance Policies | Evaluate device compliance and initiate remediation or service-management processes. | ServiceNow, Jira, Slack, identity and access platforms | Martini retrieves policy and affected-device information, applies severity and approval rules, and creates incidents or invokes permitted remediation actions. |
| Smart Groups | Target Applications, Profiles, Compliance Policies, and other device-management resources. | Workday, Microsoft Entra ID, Okta, ServiceNow | Martini derives membership or assignment criteria from authoritative systems, maps stable identifiers, and orchestrates controlled group and assignment changes. |
Authentication and security considerations
Tenant-scoped authentication
Workspace ONE UEM commonly uses administrator credentials with HTTP Basic Authentication and the aw-tenant-code header. Supported deployments may also provide OAuth 2.0, subject to tenant version, Workspace ONE Access configuration, and required scopes.
Least-privilege access
API access is constrained by administrator roles, organization-group scope, device ownership or assignment scope, and permitted operations. Use an account with only the permissions required by the workflows.
Secret protection
Store credentials, tenant codes, client secrets, and access tokens in Martini environment configuration or secrets management. Avoid embedding secrets in workflow definitions or logging complete request and response payloads.
Operational considerations for Omnissa Workspace ONE UEM integrations
Pagination and synchronization
Device, user, application, and assignment responses may be paginated. Follow documented continuation fields, persist a high-water mark where supported, and perform periodic reconciliation because not every resource has identical change tracking.
Throttling and retries
Use bounded concurrency, controlled page sizes, bulk operations where documented, and exponential backoff for 429 and transient 5xx responses. Limit retries and record failed objects for later processing.
Asynchronous operations
Bulk actions, device commands, and package operations may be accepted before completion. Track operation identifiers and poll documented status endpoints where available rather than treating an accepted request as successful completion.
Scope and schema changes
Organization-group permissions, API versions, optional fields, enumerations, nested objects, and identifier formats can vary. Store tenant configuration outside workflow logic and use explicit validation and mapping.
Operational safety
Enterprise wipe, device wipe, lock, reboot, and unenrollment actions require authorization, validation, audit logging, and appropriate approval controls. Protect device identifiers, usernames, serial numbers, compliance state, and application assignments in logs and downstream systems.
Why use Martini instead of scripts or point-to-point integrations?
Orchestrate more than API calls
Martini coordinates Workspace ONE UEM API consumption, event triggers, scheduled reconciliation, downstream writes, business rules, and controlled reverse operations in one maintainable workflow model.
Reduce point-to-point duplication
Reusable workflows and services centralize authentication, pagination, mapping, retry policies, identifier handling, and tenant-specific configuration instead of repeating them across scripts and integrations.
Support controlled change
Martini can transform version-sensitive Workspace ONE UEM payloads into canonical models, expose controlled APIs for approved operations, and provide structured error handling and monitoring for long-running or asynchronous work.
Frequently asked questions
Workspace ONE UEM is primarily integrated through REST APIs covering Devices, Users, Applications, Profiles, Smart Groups, Compliance Policies, assignments, inventory, and device actions. Selected event notifications or callbacks can support event-driven processing, while scheduled incremental synchronization and reconciliation cover changes that are not exposed as events.
Yes. Martini can consume Workspace ONE UEM REST APIs, receive supported event notifications, schedule synchronization workflows, transform JSON payloads, and expose controlled APIs for selected UEM operations. The exact API paths and authentication configuration should be confirmed for the target tenant and version.
No dedicated connector is required. Martini can integrate with Workspace ONE UEM using its confirmed native REST APIs, supported event notifications or callbacks, authentication methods, and documented file or bulk operations.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Omnissa Workspace ONE UEM. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Omnissa, cloud infrastructure, or other third-party systems depending on subscription, API usage, and deployment model.
REST APIs are the primary method for current enterprise integrations. Selected event notifications can reduce polling for supported events, while bulk or asynchronous operations are useful for larger administrative workloads. File and application-package operations should be validated against the target API version. No confirmed public GraphQL or SOAP surface was identified.
Workspace ONE UEM supports event-notification capabilities for selected device-management and administrative events. Coverage varies by event type, tenant configuration, and version, so notifications should not be treated as a complete change stream. Martini can receive supported callbacks and retrieve the current resource before processing it.
Martini can run scheduled workflows that use pagination, modified-time or status filters where available, persisted high-water marks, and periodic full or scoped reconciliation. Stable Workspace ONE UEM identifiers support idempotent upserts, while controlled concurrency and bounded retries help manage large inventories and transient failures.
Martini maps Workspace ONE UEM JSON into canonical and target-specific models, validates optional and version-dependent fields, and applies business rules before writing data. Workflows can use stable identifiers to prevent duplicates, retry transient responses with limits, distinguish accepted from completed asynchronous operations, and route unresolved failures for monitoring and review.
Related Martini documentation
Integrate Omnissa Workspace ONE UEM with Martini
Connect Workspace ONE UEM to enterprise applications through maintainable API-led workflows, selected event notifications, secure authentication, and reliable data synchronization.