Jamf Pro API

Name: Jamf Pro API
Brand: Jamf Pro API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsMonitoring Observabilitybearer, basic24 EndpointsREST

For Agents

Manage Apple device fleets — macOS computers, iOS and iPadOS mobiles, departments — through the Jamf Pro inventory and authentication APIs.

Install Jentic One Beta

Connect the Jamf Pro API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Jamf Pro API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Jamf Pro API.

Mint bearer tokens from basic-auth credentials and rotate them via the keep-alive endpoint

Inventory enrolled macOS computers and pull detailed hardware and software records

Inventory enrolled iOS and iPadOS devices and update specific record sections

GET STARTED

Start building with Jamf Pro API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Jamf Pro API for, with concrete tasks.

★ Apple Fleet Inventory Reporting

IT teams report on the state of their Mac and iOS fleet for security and asset reviews. The /api/v1/computers-inventory and /api/v2/mobile-devices endpoints return paged inventory records with hardware, OS, and enrolment data, which an integration writes to a CMDB or BI warehouse for fleet-wide reporting and trend analysis.

Page through GET /api/v1/computers-inventory and write each record to the CMDB computers table

Joiner-Mover-Leaver Device Lifecycle

When an employee leaves, IT must decommission their Mac in Jamf and remove it from inventory. PATCH /api/v1/computers-inventory/{id} updates the assignment fields and DELETE /api/v1/computers-inventory/{id} removes the record after wipe. Department updates on /api/v1/departments support reassignments during internal moves.

PATCH /api/v1/computers-inventory/{id} to clear the assignedUser field, then DELETE /api/v1/computers-inventory/{id} after the wipe completes

Department-Scoped Policy Targeting

Security teams scope policies by department — different controls for finance, engineering, and contractors. POST /api/v1/departments creates the targeting groups, GET lists them, and updates align Jamf with the org structure pulled from HR. Policies referenced in Jamf can then be scoped to the right department without manual sync.

GET /api/v1/departments to list current names and POST any missing departments returned by the HRIS export

AI Agent IT Operations Assistant

An IT operations assistant answers questions like 'how many Macs are running macOS 14?' or 'show me iPads not seen in 30 days'. Through Jentic the agent searches for 'jamf computer inventory', loads the GET /api/v1/computers-inventory schema, and executes with the bearer token managed in the Jentic vault.

Search Jentic for 'jamf computer inventory', execute GET /api/v1/computers-inventory with a section filter for OS, and aggregate the macOS version counts

Key Endpoints

24 endpoints — the jamf pro api manages apple devices — macos, ios, ipados, and tvos — across enterprise fleets.

METHOD

PATH

DESCRIPTION

POST

/api/v1/auth/token

Mint a bearer token from basic-auth credentials

POST

/api/v1/auth/keep-alive

Rotate a bearer token before expiry

POST

/api/v1/auth/invalidate-token

Invalidate the current bearer token

GET

/api/v1/computers-inventory

List enrolled macOS computers

GET

/api/v1/computers-inventory/{id}

Get a specific computer record

PATCH

/api/v1/computers-inventory/{id}

Partially update a computer record

GET

/api/v2/mobile-devices

List enrolled iOS and iPadOS devices

GET

/api/v1/departments

List organisational departments

POST

/api/v1/auth/token

Mint a bearer token from basic-auth credentials

POST

/api/v1/auth/keep-alive

Rotate a bearer token before expiry

POST

/api/v1/auth/invalidate-token

Invalidate the current bearer token

GET

/api/v1/computers-inventory

List enrolled macOS computers

GET

/api/v1/computers-inventory/{id}

Get a specific computer record

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Jamf basic-auth admin credentials are stored encrypted in the Jentic vault. Agents receive scoped execution tokens — Jentic mints and rotates the Jamf bearer token at request time so the raw credentials never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g. 'list jamf computers' or 'create department') and Jentic returns matching Jamf Pro operations with their input schemas, so the agent can call the right endpoint without consulting Jamf documentation.

Time to first call

Direct Jamf integration: 2-4 days including token lifecycle, error handling, and pagination. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Jamf Pro API through Jentic.

What authentication does the Jamf Pro API use?

The modern Jamf Pro API uses bearer tokens minted from POST /api/v1/auth/token after an initial basic-auth exchange with the Jamf admin credentials. Tokens expire and can be rotated via /api/v1/auth/keep-alive. Through Jentic the basic credentials live in the credential vault and the bearer token rotation is handled at execution time.

Can I list all enrolled Mac computers with the Jamf Pro API?

Yes. GET /api/v1/computers-inventory returns paged records with hardware, software, and enrolment details. Use section query parameters to limit the response to the fields you need so large fleets can be paged efficiently.

What are the rate limits for the Jamf Pro API?

Jamf does not publish a fixed numeric rate limit; throttling is applied per Jamf Cloud instance based on tier and CPU pressure. Treat 429 responses as a signal to back off, batch inventory pulls overnight, and cache departmental lookups locally.

How do I retrieve computer inventory through Jentic?

Search Jentic for 'jamf computer inventory', load the GET /api/v1/computers-inventory operation schema, and execute with optional section filters. Jentic handles bearer token minting and rotation so the agent only supplies query parameters.

Does this spec cover the Jamf Classic API?

No. The 11.26.0 spec covers the modern Jamf Pro API only. The Classic API is a separate XML-based interface still used for some legacy operations; if you need Classic endpoints you must integrate that interface directly outside this spec.

Can I delete a computer record from inventory?

Yes. DELETE /api/v1/computers-inventory/{id} removes the record. Pair the call with a wipe command before deletion so that the device is sanitised and removed from MDM in a single workflow.

Jamf Pro API

Connect the Jamf Pro API to your agent

Capabilities

Start building with Jamf Pro API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs