Official vendor OpenAPI document · agent-readyDeveloper 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.
Use for: I need to inventory all enrolled Mac computers, Retrieve a specific iPad's inventory record, List the departments configured in Jamf Pro, Create a new department for scoping policies
Not supported: Does not handle Windows or Android device management, software packaging, or Apple Business Manager enrolment - use for Jamf Pro Apple device inventory and core configuration only.
The Jamf Pro API manages Apple devices - macOS, iOS, iPadOS, and tvOS - across enterprise fleets. The 11.26.0 spec covers the modern Jamf Pro v1 and v2 endpoints for authentication, computer and mobile-device inventory, departments, and core device-management operations. Authentication uses bearer tokens minted from the /api/v1/auth/token endpoint after an initial basic-auth exchange, with keep-alive and invalidate flows for long-running integrations.
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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fjamf.com%2Fjamf" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fjamf.com%2Fjamf" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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
List, create, and update organisational departments used in scoping policies
Delete a computer record from inventory when a device is decommissioned
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 your Jentic One instance.
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
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
J
Jamf Pro API
- AI-Aware (B-)61/100
99
Foundational Compliance62
Developer Experience & Jentic Compatibility46
AI-Readiness & Agent Experience94
Agent Usability43
Security55
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
62
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
49%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
46
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
22%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
63%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
43
Security
Trust, risk posture, and security compliance.
Grade: D-Signals: 1
42%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
55
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: CSignals: 1
55%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Jamf Pro API by hand means exchanging basic-auth admin credentials for a bearer token, keeping that token alive, and targeting your own jamfcloud instance host yourself. Through Jentic you install once, import Jamf Pro from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Jamf Pro puts the record id in the URL path (/api/v1/computers-inventory/{id}), so a rule can pin your agent to the read operations for inventory and departments. You choose the operations it may call, so a computer-inventory update is not included unless you add it.
Credential isolation
Your Jamf admin credentials are stored once, encrypted, by your own Jentic One instance, which mints and refreshes the Jamf bearer token at execution time. The raw credentials never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list Jamf computers' or 'read a department', and Jentic returns the matching Jamf Pro operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe API
Billing platform used for Jamf reseller subscriptions and IT service fees
Use Stripe alongside Jamf when an MSP agent reconciles per-device licence billing against the Jamf inventory
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.
Can I limit what my agent is allowed to do with the Jamf Pro API?
Yes. Because Jentic One is self-hosted, you set the rules that decide which Jamf Pro operations and credentials your agent may use. You can pin the agent to read-only calls such as GET /api/v1/computers-inventory and GET /api/v1/departments, so it lists Mac computers and departments but cannot run a PATCH update or DELETE on a computer record unless you explicitly add those operations. The record id sits in the URL path, so each inventory operation is scoped separately and nothing outside your allowed set is callable.
GET STARTED