JumpCloud

JumpCloud Google EMM API

The Google EMM API from JumpCloud — 17 operation(s) for google emm.

GitHub OpenAPI

Operations 21

GET /google-emm/devices/{deviceId} Get device #
POST /google-emm/devices/{deviceId}/lock Lock device #
POST /google-emm/devices/{deviceId}/resetpassword Reset Password of a device #
GET /google-emm/enterprises List Google Enterprises #
POST /google-emm/enterprises Create a Google Enterprise #
DELETE /google-emm/enterprises/{enterpriseId} Delete a Google Enterprise #
PATCH /google-emm/enterprises/{enterpriseId} Update a Google Enterprise #
POST /google-emm/signup-urls Get a Signup URL to enroll Google enterprise #
POST /google-emm/web-tokens Get a web token to render Google Play iFrame #
GET /google-emm/devices/{deviceId}/policy_results Get the policy JSON of a device #
GET /google-emm/enterprises/{enterpriseId}/connection-status Test connection with Google #
POST /google-emm/devices/{deviceId}/erase-device Erase the Android Device #
POST /google-emm/devices/{deviceId}/reboot Reboot device #
GET /google-emm/enterprises/{enterpriseObjectId}/devices List devices #
GET /google-emm/enterprises/{enterpriseObjectId}/enrollment-tokens List enrollment tokens #
POST /google-emm/enterprises/{enterpriseObjectId}/enrollment-tokens Create an enrollment token for a given enterprise #
DELETE /google-emm/enterprises/{enterpriseId}/enrollment-tokens/{tokenId} Deletes an enrollment token for a given enterprise and token id #
GET /google-emm/enterprises/{enterpriseId}/enrollment-tokens/{tokenId} Get an enrollment token by ID #
POST /google-emm/devices/{deviceId}/lostmode/start Start lost mode #
POST /google-emm/devices/{deviceId}/lostmode/stop Stop lost mode #
POST /google-emm/enterprises/{enterpriseId}/generate-upgrade-url Generates an upgrade URL for an enterprise #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/jumpcloud/openapi/jumpcloud-google-emm-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/jumpcloud:jumpcloud-google-emm-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

jumpcloud-google-emm-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  contact:
    name: JumpCloud Support
    url: https://jumpcloud.com/support/contact-jumpcloud-support
  description: '# Overview


    JumpCloud''s V2 API. This set of endpoints allows JumpCloud customers to manage objects, groupings and mappings and interact with the JumpCloud Graph. > **Note:** See JumpCloud Data Centers: Login URLs and Service Endpoints to learn more. ## API Best Practices


    Read the linked Help Article below for guidance on retrying failed requests to JumpCloud''s REST API, as well as best practices for structuring subsequent retry requests. Customizing retry mechanisms based on these recommendations will increase the reliability and dependability of your API calls. Covered topics include:

    1. Important Considerations

    2. Supported HTTP Request Methods

    3. Response codes

    4. API Key rotation

    5. Paginating

    6. Error handling

    7. Retry rates


    JumpCloud Help Center - API Best Practices


    # Directory Objects


    This API offers the ability to interact with some of our core features; otherwise known as Directory Objects. The Directory Objects are:


    * Commands

    * Policies

    * Policy Groups

    * Applications

    * Systems

    * Users

    * User Groups

    * System Groups

    * Radius Servers

    * Directories: Office 365, LDAP,G-Suite, Active Directory

    * Duo accounts and applications. The Directory Object is an important concept to understand in order to successfully use JumpCloud API. ## JumpCloud Graph


    We''ve also introduced the concept of the JumpCloud Graph along with Directory Objects. The Graph is a powerful aspect of our platform which will enable you to associate objects with each other, or establish membership for certain objects to become members of other objects. Specific `GET` endpoints will allow you to traverse the JumpCloud Graph to return all indirect and directly bound objects in your organization. | !alt text |

    |:--:|

    | **This diagram highlights our association and membership model as it relates to Directory Objects.** |


    # API Key


    ## Access Your API Key


    To locate your API Key:


    1. Log into the JumpCloud Admin Console. 2. Go to the username drop down located in the top-right of the Console. 3. Retrieve your API key from API Settings. ## API Key Considerations


    This API key is associated to the currently logged in administrator. Other admins will have different API keys. **WARNING** Please keep this API key secret, as it grants full access to any data accessible via your JumpCloud console account. You can also reset your API key in the same location in the JumpCloud Admin Console. ## Recycling or Resetting Your API Key


    In order to revoke access with the current API key, simply reset your API key. This will render all calls using the previous API key inaccessible. Your API key will be passed in as a header with the header name "x-api-key". ```bash

    curl -H "x-api-key: [YOUR_API_KEY_HERE]" "https://console.jumpcloud.com/api/v2/systemgroups"

    ```


    # System Context


    * Introduction

    * Supported endpoints

    * Response codes

    * Authentication

    * Additional examples

    * Third party


    ## Introduction


    JumpCloud System Context Authorization is an alternative way to authenticate with a subset of JumpCloud''s REST APIs. Using this method, a system can manage its information and resource associations, allowing modern auto provisioning environments to scale as needed. **Notes:**


    * The following documentation applies to Linux Operating Systems only. * Systems that have been automatically enrolled using Apple''s Device Enrollment Program (DEP) or systems enrolled using the User Portal install are not eligible to use the System Context API to prevent unauthorized access to system groups and resources. If a script that utilizes the System Context API is invoked on a system enrolled in this way, it will display an error. ## Supported Endpoints


    JumpCloud System Context Authorization can be used in conjunction with Systems endpoints found in the V1 API and certain System Group endpoints found in the v2 API.'
  title: JumpCloud Google EMM API
  version: '2.0'
servers:
- url: https://console.jumpcloud.com/api/v2
  description: United States (US)
  x-jc-region: us
- url: https://console.eu.jumpcloud.com/api/v2
  description: European Union (EU)
  x-jc-region: eu
- url: https://console.in.jumpcloud.com/api/v2
  description: India (IN)
  x-jc-region: in
tags:


# --- truncated at 32 KB (71 KB total) ---
# Full source: https://artifacts.apis.io/jumpcloud/openapi/jumpcloud-google-emm-api-openapi.yml