API Coverage

Compare API endpoint support across different PC refresh and device management platforms. This matrix shows which features are available for each integration.

Filter by capabilities

PaginationFilteringSortingCustom fieldsWebhooks

RESOURCE	Auth	Organizations	Repositories	Artifacts	Tags
Amazon ECR
Docker Hub
GitHub Container Registry
GitLab Container Registry
Google Artifact Registry
JFrog Artifactory
Microsoft ACR
Nexus

Field Mappings

Our unified API standardizes data models across different device management providers. Below you can see how Unizo fields map to provider-specific fields for each data model.

Organizations

Details about the organization’s identity and structure

Unizo Field	Amazon ECR	Docker Hub	Google Artifact Registry	GitHub Container Registry	GitLab Container Registry	JFrog Artifactory	Microsoft ACR	Nexus
idOrganization identifier
loginOrganization username
forkFork status
changeLogModification history

Repositories

Information on repository configuration and metadata

Unizo Field	Amazon ECR	Docker Hub	Google Artifact Registry	GitHub Container Registry	GitLab Container Registry	JFrog Artifactory	Microsoft ACR	Nexus
typeRepository type
idImage identifier
descriptionRepository description
fullNameRepository name
forkWhether the repository is a fork
languageContainer language
linksDescriptive link
changeLogModification history

Artifacts

Metadata and identifiers for stored artifacts

Unizo Field	Amazon ECR	Docker Hub	Google Artifact Registry	GitHub Container Registry	GitLab Container Registry	JFrog Artifactory	Microsoft ACR	Nexus
hrefArtifact URL
idArtifact identifier
typeArtifact type
nameArtifact name
descriptionArtifact description
changeLog Modification history

Tags

Descriptive attributes of image tags in the registry

Unizo Field	Amazon ECR	Docker Hub	Google Artifact Registry	GitHub Container Registry	GitLab Container Registry	JFrog Artifactory	Microsoft ACR	Nexus
hrefTag URL
idImage identifier
typeTag type
name Tag name
descriptionTag description
changeLogModification history

Native Provider Field Support

Leveraging nativeResponse

The nativeResponse field enables you to access provider-specific features beyond our unified common data model. This feature allows you to:

• Access provider-specific device attributes not included in the common data model
• Implement custom device management workflows using native provider capabilities
• Utilize advanced MDM features unique to each platform
• Maintain compatibility with existing provider-specific integrations

Enterprise Feature

The nativeResponse field is available exclusively for Enterprise and Launch Customer subscriptions. Contact our sales team to upgrade your plan and unlock access to native provider data.

How to Use nativeResponse

{
  "id": "device-123",
  "name": "LAPTOP-JDOE-01",
  "model": "MacBook Pro 14-inch",
  "os": "macOS 14.2",
  // ... other unified fields
  "nativeResponse": {
    // Complete provider-specific response
    "general": {
      "supervised": true,
      "mdm_capable": true,
      "report_date": "2024-01-15T10:30:00Z"
    },
    "hardware": {
      "battery_capacity": 85,
      "boot_rom": "10151.61.4",
      "processor_architecture": "arm64e"
    },
    "security": {
      "activation_lock_enabled": true,
      "firewall_enabled": true,
      "secure_boot_level": "full",
      "system_integrity_protection_enabled": true
    },
    "extension_attributes": [
      {
        "id": 1,
        "name": "Asset Tag",
        "value": "COMP-2024-0123"
      }
    ]
  }
}

Need Something More?

Working on a unique device management integration? Need extra fields for your MDM tools? We're here to help.

Get in touch:

• Email: support@unizo.ai
• Web: Contact Us

We'd love to hear about your use case and help expand our API to meet your needs.