Who can use this feature?
👤 Organizations Owners, Admins, and custom roles with the "Create Access Tokens" feature.
🚩 Available on the Essential, Classroom Pro, and Enterprise Plans.
Overview
The ArborXR Public API v3 provides access to your organization’s data via a RESTful interface.
With API v3, we have transitioned from Organization-level access to User-based scoping. While v2 provided a broad foundation for integration, v3 is designed to give your team granular control and deeper visibility into every programmatic action.
By shifting the scope to individual users, we’ve introduced two critical enhancements:
Granular Access Control: A user’s API capabilities are strictly tied to their assigned role and permissions within the platform. If they don’t have permission to perform an action in the UI, they can’t do it via the API.
Enhanced Audit Transparency: Accountability is no longer a guessing game. Every API request is now tied to a specific user email in the Audit Log, making it easy to track "who did what and when" across your entire organization.
The root of v3 of the API is located at https://api.xrdm.app/api/v3 . From the documentation page, you can download the OpenAPI spec documentation as JSON or YAML, for use with your API development client of choice.
API v2 Deprecation Notice & Migration Guide
API v2 is scheduled for deprecation on May 15th, 2026. Please begin your migration to v3 as soon as possible to ensure an uninterrupted workflow. If you have any questions, our team is here to help at support@arborxr.com.
Key Deadlines & Resources:
May 15th, 2026: API v2 will be sunset and stop functioning.
The CLI: A new version of the ArborXR CLI (powered by v3) will be released on the deprecation date.
Generate an Access Token
Navigate to organization Settings.
Select Access Token.
Click Create Access Token in the top right.
Select MDM API v3 from the dropdown.
Enter a title then click Create.
Copy the token value before closing.
Authentication
Once you’ve generated an access token, you can use that token to make HTTP requests to the API, by adding it as a bearer token to your request’s Authorization header. You should also be sure to include the Accept and specify that you expect a JSON response.
Authorization: Bearer <access_token>
Accept: application/json



