Deploy Jamf Security configuration profiles to UEM

post

https://{region}.api.jamfcloud.com/securitycloud/uem-connect/v1/activation-profiles/{code}/deploy-to-uem

Deploys Jamf Security configuration profiles to the UEM platform for the specified
activation profile. This is the final step of automated UEM Connect onboarding.

Note: The activation profile code is obtained from the Jamf Security setup flow and is
not issued by the UEM Connect API. This operation is idempotent.

Requires a connector that is connected to its UEM platform and not disabled — otherwise
422 CONNECTOR_NOT_CONNECTED or 409 CONNECTOR_DISABLED respectively. Returns
409 MULTIPLE_ACTIVATION_PROFILES if the tenant has more than one active activation profile
and the deployment target is ambiguous.

Required Permissions: uem-connect:update

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

code

string

required

The activation profile code obtained from the Jamf Security setup flow

Body Params

Request to deploy activation profile configuration profiles to UEM

uem

string

enum

required

The UEM platform to deploy profiles to

Allowed:

platform

string

enum

required

The device platform type for the configuration profile

Allowed:

uemGroups

array of strings

Optional UEM group IDs to scope the deployment to.

Group names are not accepted. These are the UEM's own group IDs — for Jamf Pro, obtain
them from the Jamf Pro API (GET /v1/computer-groups, GET /v1/mobile-device-groups).
An ID is either bare numeric ("123") or device-type-prefixed ("computer_123",
"mobile_456"); a prefix, when present, must match the device type the platform
deploys to. IDs are scoped to a single UEM instance.

Scoping is additive: the IDs are merged into the configuration profile's existing scope,
so a later deploy can widen the scope but cannot narrow or clear it. Omitting the field
or sending an empty array leaves any existing scope untouched — on the first deploy of a
profile it means no group scope is set, not that the profile is scoped to every group.

uemGroups

Headers

X-Tenant-Id

uuid

required

^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$

The tenant UUID identifier.

Responses

204

Profiles deployed successfully

Language

Credentials

OAuth2

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

415Unsupported media type — the request body Content-Type is not one this operation accepts, or it was omitted. Send application/json. Error code: UNSUPPORTED_MEDIA_TYPE.

503Service unavailable — the UEM platform could not be reached or returned an error. Retry later. Error code: UEM_UNAVAILABLE.