Guide

JAMF Connection

This page explains the out-of-the-box JAMF connection profile in ABM Warranty. This is specifically for the prebuilt JAMF profile, not the Builder profile. The JAMF profile is designed to reduce setup complexity by providing predefined endpoint behavior and default mapping expectations for the ABM warranty fields used by outbound sync.

Purpose

The JAMF profile defines a known outbound integration contract for JAMF Pro. It lets you authenticate once, validate the connection, and then focus on mapping review and sync behavior. You are not required to manually design every endpoint contract in the way Builder requires.

Scope

The JAMF profile supports outbound sync of ABM warranty-related values to JAMF records and uses serial number as the record matching key. The profile includes expected destination field names and endpoint patterns suitable for JAMF API workflows.

JAMF Connection Wizard Flow

Step 1: Connection Basics + OAuth Details

Enter friendly name, base URL, token URL, OAuth client ID, and client secret. Optional values such as scope/audience may exist depending on profile fields, but required fields are validated before continuing.

Step 2: Connection Validation (Not Shown)

The wizard validates authentication and confirms the profile can communicate with destination APIs. For JAMF profile flows, this step is intended to be deterministic: when validation succeeds, the flow advances to mapping review instead of requiring manual contract design. This step is typically shown by a progress spinner and authenticates very fast assuming that your information is correct, if not its kicked back to step 1. Your Jamf Pro API Client needs the following privileges: Read Computers, Update Computers, Read Mobile Devices, Update Mobile Devices, Read Users, Update Users.

Step 3: Field Mapping Review

You review ABM source fields, destination field selections, destination sample values, and action rules. This is where you confirm update behavior prior to save.

Step 1 Enter the information into the JAMF API Connection Wizard

Enter the information into the JAMF API Connection Wizard.

Step 3 Update Mapping fields for purchasing data

Update Mapping fields for purchasing data.

Understanding Mapping in JAMF Profile

Key Matching Field

Serial number is the lookup key used to find destination records. This key should not be mapped as a field to overwrite destination identity. It is used for matching.

Default Warranty Field Set

Current warranty mapping surfaces these core ABM fields:

  • serialNumber
  • orderNumber
  • orderDateTime
  • purchaseSourceType
  • purchaseSourceId
  • appleCareId
  • warrantyDate
  • lifeExpectancy
Mapped Connections in ABM Warranty

Action Rules

Per-field action controls define behavior:

  • Update: field is eligible for outbound update.
  • Skip: field is never updated by outbound sync.
  • Key: identity/match behavior (used for serial matching context).

Even when action is Update, sync logic may still skip a field when source and destination values are already equivalent after normalization.

How to Update Mappings Later

  • Settings → Connections.
  • Select the JAMF connection row.
  • Choose Update Mapping.
Use the manual mapped connections to update connection mapping later

Review Device Type Scope

Use the device type selector to switch between Computers and Mobile Devices where available. Mapping drafts and sample snapshots are scope-aware and should be reviewed per scope before save.

Confirm Destination Samples

Destination sample values are used for operator confidence while mapping. If samples are empty, validate API auth, path contract behavior, and serial lookup viability before concluding mapping is incorrect.