--- title: Getting started with the management API framework: devicemanagement role: article role_heading: Article path: devicemanagement/getting-started-with-the-management-api --- # Getting started with the management API Configure your MDM client to handle content and user assignments. ## Overview Overview Content managers use Apple School Manager and Apple Business Manager to purchase apps, books, and subscriptions for their organization. Your MDM client then assigns these assets to users and devices. If a user no longer needs an app or subscription, your MDM client can reclaim it and reassign it to a different user. You can also assign an app directly to a device’s serial number, so an Apple Account isn’t necessary to download the app. Books and subscriptions aren’t device-assignable, and books can’t be reassigned among users. Authenticate All server endpoints except Service Config require a content token (sToken) to authenticate an organization. A valid sToken allows an MDM client to manage assets for the specified location of an organization. Only one MDM client should manage a single location at any time. Multiple MDM clients managing the same location result in unpredictable asset allocation. Content managers can download a location-based sToken from the Apps and Books section under the Settings tab in Apple School Manager or Apple Business Manager, and upload it into their MDM client. The MDM client stores the location-based content token along with its other private, protected properties, and passes this token in the Authorization header of API requests. The sToken is a JSON string in Base64 encoding. When the server decodes it, the resulting JSON string contains three fields: token, expDate, and orgName. | | | | The following is an example sToken value: ewogICAgInRva2VuIjogIlZGZHdRbVZWTVZSUldGSktVbGRTTlZkc1pHcGpNR3hIVTI1Q2FrMXRhRzlhUjJ3eldqRkdkVk50ZUd0VFJrWjZVMVZhVDJGSFRuUlNiVGxOVVRCS1ExcEdhRTlOUjBaWVRrUXdQUT09IiwKICAgICJleHBEYXRlIjogIjIwMzAtMTEtMDhUMjI6MzM6MjIrMDAwMCIsCiAgICAib3JnTmFtZSI6ICJPUkcxMjM0NSIKfQ== This is the JSON result after Base64 decoding: { "token": "VFdwQmVVMVRRWFJKUldSNVdsZGpjMGxHU25Cak1taG9aR2wzWjFGdVNteGtTRkZ6U1VaT2FHTnRSbTlNUTBKQ1pGaE9NR0ZYTkQwPQ==", "expDate": "2030-11-08T22:33:22+0000", "orgName": "ORG12345" } If the token expires within 15 days, the response contains an additional field, tokenExpirationDate. The value of this field is the expiration date in ISO-8601 format, such as the following: { ... "tokenExpirationDate": "2030-11-08T22:33:22+0000" } Handle permissions Organization administrators can tailor different sets of privileges for an individual content manager’s sToken using Managed Apple Accounts, which allows a fine level of control over what those users can do. For example, a content manager with read-only privileges can use the Get Assets, Get Assignments, and Get Users endpoints, but can’t use the User management or Asset management endpoints. Administrators can also assign content managers the Can Purchase and the Can Manage privileges, so that an individual content manager can manage assets, but not buy them. Identify the current MDM client To protect against another MDM client managing the same location, be sure to set MdmInfo in Client Config. Then inspect MdmInfo each time a response returns to ensure that no other MDM client overwrites it. MdmInfo resembles the following: { "mdmInfo": { "id": "522d5c43-44ca-4f7e-ba7a-53570cf60765", //Unique identifier. "name": "Apple Configurator 2", //MDM client name. "metadata": "2.13.3" //Freeform metadata field. }, ... } Import users After authenticating, perform an initial import of the location’s active users. Send a request to Get Users with includeRetired=0, then record the user data for each element of users in the GetUsersResponse. If the response includes a nextPageIndex, send another request with that value as the pageIndex query parameter and record the new page of users. Continue paging until currentPageIndex equals totalPages. For more information about managing users after importing them, see User management. Sync users after import Keep the imported user list up to date by passing the versionId from each response as the sinceVersionId query parameter in subsequent requests. Subsequent responses contain only users modified since that version. For more information about versioned queries and page-index pagination, see Using paginated endpoints. Import assigned assets Import asset counts first, then import the current assignments for each asset. Send a request to Get Assets to retrieve counts by adamId for the managed location. For each adamId in the GetAssetsResponse, send a request to Get Assignments and record the adamId, pricingParam, and clientUserId or serialNumber for each assignment in the GetAssignmentsResponse, along with the currentPageIndex and totalPages. Page through the results by passing the nextPageIndex value as the pageIndex query parameter in subsequent requests until currentPageIndex equals totalPages. For more information about managing assets after importing them, see Asset management. Sync assets and assignments after import Keep assignment data current by passing the versionId from each Get Assignments response as the sinceVersionId query parameter in later requests to retrieve only the assignments modified since that version. Get Assets returns a versionId in its response but doesn’t accept sinceVersionId as a filter. To reconcile asset counts, refetch the full asset list and compare the stored versionId to detect when the underlying data changed. For more information about versioned queries and page-index pagination, see Using paginated endpoints. Import subscriptions To import a location’s subscriptions, send a request to Get Subscriptions. Filter by parentAdamId or adamId, or omit both to retrieve all subscriptions. The response includes seat counts broken down by renewal state — each subscription reports how many seats are renewing (auto-renewing at the end of the billing period) and how many are expiring (not renewing). This endpoint uses cursor-based pagination instead of page-index pagination. Pass the nextCursor value from each response as the cursor query parameter in the next request, and continue until nextCursor is absent. To import per-user subscription assignments, send a request to Get Subscription Assignments. Each assignment includes a renewing Boolean value that reflects the renewal state of the seat assigned to that user. This endpoint also uses cursor-based pagination. For more information about managing subscriptions, see Managing subscriptions. Reconcile subscriptions after import The subscription endpoints don’t support sinceVersionId, so reconcile subscription data by refetching the full dataset on a schedule that matches your freshness requirements. Subscribe to SUBSCRIPTION_COUNT and SUBSCRIPTION_MANAGEMENT notifications for real-time updates between scheduled syncs. For more information about cursor-based pagination, see Using paginated endpoints. ## See Also ### Getting started - [Apps and books metadata for organizations](devicemanagement/apps-and-books-metadata-for-organizations.md)