Not found — the referenced connector or resource does not exist. Error codes: NOT_FOUND — the referenced connector or resource does not exist for the tenant; NO_ACTIVATION_PROFILE — the tenant has no active activation profile to deploy (only emittable by deployActivationProfile). Not every code applies to every operation — check the individual operation's description.

Conflict — the request cannot proceed against the current state of the tenant's connectors. Error codes: CONNECTOR_DISABLED — the connector is disabled (triggerSync, deployActivationProfile); CONNECTOR_CONFIG_ALREADY_EXISTS — the tenant already has a connector whose UEM vendor cannot coexist with the requested one, only Jamf Pro and Wizy may coexist (createConnector); UNSUPPORTED_UEM_VERSION — the UEM platform reported a version this integration does not support (createConnector); MULTIPLE_ACTIVATION_PROFILES — the tenant has more than one active activation profile, so the deployment target is ambiguous (deployActivationProfile). Not every code applies to every operation — check the individual operation's description.

Unprocessable entity. This API returns 422 for both schema-level and business-rule failures. Error codes: VALIDATION_FAILED — malformed JSON, a missing or mistyped required field, or a constraint violation (the field property identifies the offending body field where known); VENDOR_MISMATCH — the body vendor of an updateSyncSettings request does not match the connector's stored vendor; CONNECTOR_NOT_CONNECTED — the connector's credentials are not valid against the UEM platform; CONNECTOR_MISCONFIGURED — the UEM platform rejected the connector configuration.
Note that connector creation can also fail with 400 when the connection test itself fails — see the 400 response on that operation.

Service unavailable — the sync could not be dispatched because the service's sync workers are saturated or the instance is shutting down. No sync run is left in progress, so the request can be retried. Error code: SYNC_DISPATCH_REJECTED.