> ## Documentation Index > Fetch the complete documentation index at: https://docs.iru.com/llms.txt > Use this file to discover all available pages before exploring further. # Renew, update, or delete ADE tokens via the Iru API > Renew, update, or delete Automated Device Enrollment tokens with the Iru Endpoint API to prevent expiration and maintain Apple Business connections. **Apple Business Manager** is now **Apple Business**. **Apple School Manager** is unchanged. For more information, see [Introducing Apple Business](https://www.apple.com/newsroom/2026/03/introducing-apple-business-a-new-all-in-one-platform-for-businesses-of-all-sizes/) and [Apple Business Manager is now Apple Business](https://support.apple.com/guide/apple-business-manager/apple-business-manager-is-now-apple-business-axmd79d79dea/web). ### About ADE Token Management Automated Device Enrollment (ADE) tokens require periodic renewal and management to maintain device enrollment capabilities. This process allows you to efficiently manage multiple ADE tokens using API automation, reducing manual effort and ensuring consistent token lifecycle management. ### How It Works ADE token management involves using the Iru Endpoint API through Postman to perform bulk operations on multiple tokens. The process includes configuring API access, setting up environment variables, downloading tokens from Apple Business or Apple School Manager, and using automated workflows to renew, update, or delete tokens efficiently. If you do not feel confident in completing this process yourself, please reach out to [Iru Endpoint Support](/en/iru/iru-support/access-to-iru-support) for additional guidance. ### Prerequisites * Access to Iru Endpoint with API token creation permissions * Postman application installed and configured * Access to Apple Business or Apple School Manager * Multiple ADE tokens that need renewal or management * Basic understanding of API operations and Postman workflows ### Configuring an Iru Endpoint API token Prepare an API token and store it in a secure location. You can read more about this in our [Iru Endpoint API](/en/endpoint/api/iru-api-overview) article. You can skip this section if you already have an API token prepared. Create a new API token or modify an existing one with the required permissions. In your Iru Endpoint tenant, in the sidebar, click the [**Account Menu Button**](/en/iru/platform-overview/account-menu), then select **Access** → **API tokens**. Screenshot of the account menu with Access option highlighted Create or modify the existing API token to include all Automated Device Enrollment-related permissions. Access page showing API tokens for configuring ADE token permissions ### Preparing Postman Most of the steps moving forward will be performed inside the Postman application on your device. You can skip this section if you already have Postman configured. Check your Collection for the Automated Device Enrollment integrations folder. Define your API URL if undefined in the Iru Endpoint API folder at the top of the collection. Define the API Token in your Environment variables following our How to Set Up the Iru Endpoint API in Postman article. ### Configuring Postman Environment Variables Now that the basics of Postman have been configured, you will need to define some Environment Variables in Postman to keep track of the Automated Device Enrollment servers. In Postman, click the **Environments** tab in the left sidebar, then click **Create Environment** to create a new environment. Name your environment (e.g., "Iru Endpoint API") and add the following variables: * **Variable**: `base_url` * **Initial Value**: `https://.api.iru.com/api/v1` * **Current Value**: `https://.api.iru.com/api/v1` Replace `` with your tenant's actual subdomain, or copy the base URL directly from your tenant. The URL shown in your tenant may use the `api.kandji.io` domain. Both `.api.iru.com` and `.api.kandji.io` will work without modification. * **Variable**: `token` * **Initial Value**: `your_api_token_here` * **Current Value**: `your_api_token_here` Click **Save** to save your environment, then select your newly created environment from the environment dropdown in the top-right corner. If you already have environment variables configured, you can add the new items to the existing variables. Navigate to **Iru Endpoint API** > **Automated Device Enrollment Integrations** > **GET List ADE Integrations** in the Collection. Click the **Send** button to execute the request. Postman Collection showing Automated Device Enrollment Integrations folder and GET List ADE Integrations request In the **Body** section of the Results, copy the top-level IDs of each Automated Device Enrollment token. For each token ID, create an environment variable with a naming scheme such as `ade_token_1`, `ade_token_2`, etc., incrementing the number for each token. Make a note of the associated `server_name` for each token. You will need this information when downloading the tokens from Apple Business or Apple School Manager. Postman request Body section showing ADE token IDs to copy for environment variables Paste the ID value for each token into the corresponding `ade_token_#` variable (e.g., `ade_token_1`, `ade_token_2`). You can set the variable type to secret so that the value of the variable is not visible. Postman Environments tab showing Create Environment and variables for base_url and token ### Downloading ADE Tokens Sign in to your [Apple Business](https://business.apple.com) or [Apple School Manager](https://school.apple.com) account. Click the **Devices** tab at the top of the page. In the left sidebar, click **Management**. In the **Management Services** list, select the service whose name matches the first ADE integration's `server_name` from the list you made earlier in Postman. Apple Business or Apple School Manager Management Services list with an existing device management service Click the ellipsis (**…**) for that service. Click **Download Token**. Apple Business or Apple School Manager Download Service Token action Repeat this process for each token that you will be renewing. ### Creating Postman Folder Template Creating folders in Postman will make it easier to keep track of your Automated Device Enrollment tokens. Click on the ellipsis next to the Automated Device Enrollment Integrations folder. Click Add folder. Postman Collection showing Add folder and ADE_Token1 folder with Renew and Update ADE Integration items Name the folder ADE\_Token1. Navigate to the **Automated Device Enrollment Integrations** folder and select the **Renew ADE Integration** and **Update ADE Integration** items. Right-click the selected items and choose **Copy**. Click on the ellipsis next to the ADE\_Token1 folder. Click **Paste** to add the copied items to the new folder. ### Modifying Renew Item Select the **Renew ADE Integration** item from your token folder. Rename it to **Renew ADE1 Integration** (or **Renew ADE2 Integration**, etc., based on your token number). In the section to the right, click on the address bar to the left of the **Send** button. Select the text inside `{{ade_token_ade}}` and update it to `{{ade_token_1}}` (or `{{ade_token_2}}`, etc., based on your token number). Click on the Body tab below. Enter the `blueprint_id`, phone, and email that should be associated with the token. Postman Renew ADE Integration request showing address bar with token variable and Body tab with blueprint_id, phone, email, and file upload For the file, click x by any current files, and then click Select Files. Choose the .p7m file that matches this ADE token. Save the changes. ### Modifying Update Item Select the **Update ADE Integration** item from your token folder. Rename it to **Update ADE1 Integration** (or **Update ADE2 Integration**, etc., based on your token number). In the section to the right, click on the address bar to the left of the **Send** button. Select the text inside `{{ade_token_ade}}` and update it to `{{ade_token_1}}` (or `{{ade_token_2}}`, etc., based on your token number). Click on the Body tab below. This is where you can enter new `blueprint_id`, phone, and email information. Save the changes. Postman Update ADE Integration request showing Body section for blueprint_id, phone, and email updates ### Duplicating ADE\_Token Folder Click on the ellipsis next to the ADE\_Token1 folder. Choose Duplicate. Postman folder ellipsis menu showing Duplicate option for ADE token folder Update the contents of the folder using the process above. Make duplicates of the folder for each of your ADE tokens. ### Renewing ADE Integration Now that everything is configured, you can send the Renew command. Navigate to the specific token folder you created (e.g., **ADE\_Token1**, **ADE\_Token2**, etc.) and select the **Renew ADE1 Integration** (or **Renew ADE2 Integration**, etc.) item that corresponds to your token number. Click the Send button. Postman Renew ADE Integration request with Send button to execute renewal ### Updating ADE Integration Updating the ADE Integration will allow you to change the associated Blueprint ID, phone number, and email address. Navigate to the specific token folder you created (e.g., **ADE\_Token1**, **ADE\_Token2**, etc.) and select the **Update ADE1 Integration** (or **Update ADE2 Integration**, etc.) item that corresponds to your token number. Update the details in the Body section that need updating. Click the Send button. Postman Update ADE Integration request with Send button to execute update ### Checking Current Integrations Iru Endpoint API > Automated Device Enrollment Integrations > GET List ADE Integrations command will give us all current ADE integrations so that we can verify that the integration was Renewed or Updated successfully. Select Iru Endpoint API > Automated Device Enrollment Integrations > GET List ADE Integrations in the Collection. Click the Send button. The `days_left` variable should be 364 if the Renew command was successful. To verify an update, check the information associated with the ADE token to verify that it was updated. Postman GET List ADE Integrations response showing days_left and integration details for verification ### Deleting Integration Iru Endpoint API > Automated Device Enrollment Integrations > DEL Delete ADE Integration command will delete the ADE integration associated with the supplied ADE Token ID. Select Iru Endpoint API > Automated Device Enrollment Integrations > DEL Delete ADE Integration in the Collection. Populate the `ade_token_id` variable with the ID of the ADE Token. Click the Send button. Postman DEL Delete ADE Integration request with ade_token_id variable and Send button ### Considerations * **API Token Security**: Ensure API tokens are stored securely and have appropriate permissions for ADE operations * **Postman Configuration**: Proper Postman setup is essential for successful API operations * **Environment Variables**: Use environment variables to manage multiple token IDs efficiently * **Error Handling**: Be prepared to troubleshoot API errors and token validation issues * **Token Lifecycle**: ADE tokens have expiration dates and require periodic renewal to maintain enrollment capabilities * **Token File Management**: Keep track of downloaded .p7m files and associate them with correct token IDs * **Apple Business or Apple School Manager access**: Ensure you can sign in to the portal and download tokens * **Verification Process**: Always verify successful operations by checking integration status and token expiration * **Bulk Operations**: Use folder templates to efficiently manage multiple tokens * **Access Control**: Ensure only authorized personnel have access to token management operations * **Testing**: Test operations on a small scale before performing bulk operations * **Monitoring**: Regularly monitor token expiration dates and renewal schedules * **Documentation**: Keep records of token configurations and associated server names * **Backup Strategy**: Maintain backups of token configurations and API settings