Autodesk BIM 360 OAuth Scopes
Autodesk BIM 360 publishes 17 OAuth 2.0 scopes via the clientCredentials, implicit, and authorizationCode flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Autodesk BIM 360 API on a user’s behalf.
This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.
Scopes (17)
| Scope | Description | Flows |
|---|---|---|
| user-profile:read | The application will be able to read the end user's profile data (not including associated products and services). | |
| user:read | The application will be able to read the end user's profile data, including associated products and services. | |
| user:write | The application will be able to create, update, and delete the end user's profile data, including associated products and services. | |
| viewables:read | The application will only be able to read the end user's viewable data (e.g., PNG and SVF files) within the Autodesk ecosystem. | |
| data:read | The application will be able to read all the end user's data (viewable and non-viewable) within the Autodesk ecosystem. | |
| data:write | The application will be able to create, update, and delete data on behalf of the end user within the Autodesk ecosystem. | |
| data:create | The application will be able to create data on behalf of the end user within the Autodesk ecosystem. | |
| data:search | The application will be able to search the end user's data within the Autodesk ecosystem. | |
| bucket:create | The application will be able to create an OSS bucket it will own. | |
| bucket:read | The application will be able to read the metadata and list contents for OSS buckets that it has access to. | |
| bucket:update | The application will be able to set permissions and entitlements for OSS buckets that it has permission to modify. | |
| bucket:delete | The application will be able to delete a bucket that it has permission to delete. | |
| code:all | The application will be able to author and execute code on behalf of the end user (e.g., scripts processed by the Design Automation API). | |
| account:read | For Product APIs, the application will be able to read the account data the end user has entitlements to. | |
| account:write | For Product APIs, the application will be able to update the account data the end user has entitlements to. | |
| openid | The application requires this scope to generate an id_token. | |
| data:read: |
Dynamic scope that allows the client to access only the specific resource with the URN/Object ID specified by |
📄 Provider scope reference: https://aps.autodesk.com/en/docs/oauth/v2/developers_guide/scopes/
Source
OAuth Scopes
Work with this as data
Every scope set 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 oauth scopes
4 MCP tools reach this
find_scopesBrowse and filter every scope set in the catalog.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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/scopes/autodesk-bim360-scopes"
curl "https://apis.io/api/v1/scopes?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.