JAMF

Jamf is the standard in managing and securing Apple devices at scale for business, education, and government. Its cloud platform pairs Apple device management (MDM), identity, and endpoint security with a broad developer surface: the modern Jamf Pro API (OpenAPI 3.0, bearer-token and OAuth client-credential API Roles & Clients), the long-standing Classic API (/JSSResource, XML/JSON), the new unified Platform API Gateway (Blueprints, Compliance Benchmarks, Device Management Actions), plus the Jamf School, Jamf Protect, and Jamf Security APIs. Jamf publishes an llms.txt developer index, a hosted MCP server for documentation and code generation, a webhooks event catalog, and a trust center enumerating SOC 2, ISO 27001/27701, PCI DSS, HIPAA, GDPR, and NIST 800-53 posture.

JAMF publishes 1 API on the APIs.io network: Pro API. Tagged areas include Company, Apple Device Management, MDM, Endpoint Security, and Mobile Device Management.

The JAMF catalog on APIs.io includes 1 event-driven AsyncAPI specification.

JAMF’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, pricing, signup flow, and 23 more developer resources.

🌐 Visit website 📡 Source on GitHub
51.9/100 developing Agent 51/100 agent ready Full breakdown ↓
scored 2026-07-20 · rubric v0.4
3 APIs 1 MCP Servers 0 Features
CompanyApple Device ManagementMDMEndpoint SecurityMobile Device ManagementIT OperationsIdentityComplianceDeveloper ToolsEnterprise

API Rating

API Evangelist API Evangelist Rating How this is scored →
scored 2026-07-20 · rubric v0.4
Composite quality — 51.9/100 · developing
Contract Quality 9.4 / 25
Developer Ergonomics 12.2 / 20
Commercial Clarity 12.1 / 20
Operational Transparency 8.2 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 51/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 6 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 3 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/jamf: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs

Jamf Pro API

The modern Jamf Pro API, built on the OpenAPI 3.0 standard, for programmatically managing computers, mobile devices, policies, groups, inventory, and configuration on a Jamf Pro...

Jamf Pro Classic API

The long-standing Classic API, the original resource for programmatically interacting with Jamf Pro, located at /JSSResource on each instance. Supports XML and JSON payloads and...

Jamf Platform API Gateway

A single, unified gateway to access any combination of Jamf APIs — Blueprints, Compliance Benchmarks, Device Management Actions, Declaration Reporting, Devices, and Device Group...

MCP Servers

jamf-mcp.yml

MCP SERVER

Event Specifications

Jamf Webhooks

ASYNCAPI

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 GettingStarted
GettingStarted
 SignUp
SignUp

Documentation 2

Reference material describing how the API behaves

Documentation
Documentation
 APIReference
APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt
LLMsTxt
 WellKnown
WellKnown
 MCPServer
MCPServer

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Webhooks
Webhooks
 Conventions
Conventions
 Lifecycle
Lifecycle
 Conformance
Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization

Access & Security 7

Authentication, authorization, and security posture

VulnerabilityDisclosure
VulnerabilityDisclosure
 DomainSecurity
DomainSecurity
 SecurityTxt
SecurityTxt
 Authentication
Authentication
 Compliance
Compliance
 TrustCenter
TrustCenter
 Security
Security

Scroll for all 7

Operate 4

Status, limits, changes, and where to get help

Support
Support
 StatusPage
StatusPage
 ChangeLog
ChangeLog
 Deprecation
Deprecation

Commercial 3

Pricing, plans, and the legal terms of use

Pricing
Pricing
 TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy

Company 2

The organization behind the API

Website
Website
 Blog
Blog

Other 1

Properties that don't map to a standard resource type

APICatalog
APICatalog

Source (apis.yml)

apis.yml Raw ↑ 
aid: jamf
name: JAMF
description: 'Jamf is the standard in managing and securing Apple devices at scale for business, education, and government.
  Its cloud platform pairs Apple device management (MDM), identity, and endpoint security with a broad developer surface:
  the modern Jamf Pro API (OpenAPI 3.0, bearer-token and OAuth client-credential API Roles & Clients), the long-standing Classic
  API (/JSSResource, XML/JSON), the new unified Platform API Gateway (Blueprints, Compliance Benchmarks, Device Management
  Actions), plus the Jamf School, Jamf Protect, and Jamf Security APIs. Jamf publishes an llms.txt developer index, a hosted
  MCP server for documentation and code generation, a webhooks event catalog, and a trust center enumerating SOC 2, ISO 27001/27701,
  PCI DSS, HIPAA, GDPR, and NIST 800-53 posture.'
url: https://raw.githubusercontent.com/api-evangelist/jamf/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- battery-ventures
x-tier: profiled
x-tier-reason: enrichment-pipeline
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-19'
image: https://www.jamf.com/favicon.ico
tags:
- Company
- Apple Device Management
- MDM
- Endpoint Security
- Mobile Device Management
- IT Operations
- Identity
- Compliance
- Developer Tools
- Enterprise
apis:
- name: Jamf Pro API
  description: The modern Jamf Pro API, built on the OpenAPI 3.0 standard, for programmatically managing computers, mobile
    devices, policies, groups, inventory, and configuration on a Jamf Pro instance. Authenticated with bearer tokens or OAuth
    client-credential API Roles & Clients.
  humanURL: https://developer.jamf.com/jamf-pro/reference/jamf-pro-api
  baseURL: https://your-instance.jamfcloud.com/api
  properties:
  - type: Documentation
    url: https://developer.jamf.com/jamf-pro/docs
  - type: APIReference
    url: https://developer.jamf.com/jamf-pro/reference/jamf-pro-api
  - type: OpenAPI
    url: https://your-instance.jamfcloud.com/api/schema
- name: Jamf Pro Classic API
  description: The long-standing Classic API, the original resource for programmatically interacting with Jamf Pro, located
    at /JSSResource on each instance. Supports XML and JSON payloads and bearer-token authentication.
  humanURL: https://developer.jamf.com/jamf-pro/reference/classic-api
  baseURL: https://your-instance.jamfcloud.com/JSSResource
  properties:
  - type: APIReference
    url: https://developer.jamf.com/jamf-pro/reference/classic-api
- name: Jamf Platform API Gateway
  description: A single, unified gateway to access any combination of Jamf APIs — Blueprints, Compliance Benchmarks, Device
    Management Actions, Declaration Reporting, Devices, and Device Groups — described as the long-term future of APIs at Jamf.
  humanURL: https://developer.jamf.com/platform-api
  baseURL: https://developer.jamf.com/platform-api/reference
  properties:
  - type: APIReference
    url: https://developer.jamf.com/platform-api/reference
common:
- type: VulnerabilityDisclosure
  url: security/jamf-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/jamf-domain-security.yml
- type: Website
  url: https://www.jamf.com/
- type: DeveloperPortal
  url: https://developer.jamf.com/
- type: Documentation
  url: https://developer.jamf.com/jamf-pro/docs
- type: APIReference
  url: https://developer.jamf.com/jamf-pro/reference/jamf-pro-api
- type: GettingStarted
  url: https://developer.jamf.com/developer-guide
- type: Blog
  url: https://www.jamf.com/blog/
- type: GitHubOrganization
  url: https://github.com/jamf
- type: Support
  url: https://www.jamf.com/support/
- type: Pricing
  url: https://www.jamf.com/pricing/
- type: SignUp
  url: https://www.jamf.com/request-trial/
- type: TermsOfService
  url: https://www.jamf.com/terms-of-use/
- type: PrivacyPolicy
  url: https://www.jamf.com/trust-center/privacy/
- type: StatusPage
  url: https://status.jamf.com/
- type: ChangeLog
  url: https://developer.jamf.com/jamf-pro/changelog
- type: LLMsTxt
  url: llms/jamf-llms.txt
- type: WellKnown
  url: well-known/jamf-well-known.yml
- type: APICatalog
  url: well-known/jamf-api-catalog.json
- type: SecurityTxt
  url: well-known/jamf-security.txt
- type: MCPServer
  url: mcp/jamf-mcp.yml
- type: Webhooks
  url: asyncapi/jamf-webhooks.yml
- type: Authentication
  url: authentication/jamf-authentication.yml
- type: Conventions
  url: conventions/jamf-conventions.yml
- type: Lifecycle
  url: lifecycle/jamf-lifecycle.yml
- type: Deprecation
  url: lifecycle/jamf-lifecycle.yml
- type: Conformance
  url: conformance/jamf-conformance.yml
- type: Compliance
  url: security/jamf-trust-center.yml
- type: TrustCenter
  url: security/jamf-trust-center.yml
- type: Security
  url: https://www.jamf.com/trust-center/vulnerability-disclosure/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence