Autodesk · OAuth Scopes

Autodesk OAuth Scopes

OAuth 2.0 searched

Autodesk publishes 15 OAuth 2.0 scopes via the authorizationCode and clientCredentials flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Autodesk API on a user’s behalf.

Tokens are issued from https://developer.api.autodesk.com/authentication/v2/token.

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.

Digital TwinAutodeskFortune 10003D ModelingArchitectureBIMCADConstructionDesignEngineeringManufacturingMedia and EntertainmentSustainability

Scopes: 15 Flows: authorizationCode, clientCredentials Method: searched

OAuth endpoints

Authorization URL
https://developer.api.autodesk.com/authentication/v2/authorize

Token URL
https://developer.api.autodesk.com/authentication/v2/token

Flows
authorizationCodeclientCredentials

Scopes (15)

Scope	Description	Flows
account:read	For Product APIs, the application will be able to read the account data the end user has entitlements to.	authorizationCode, clientCredentials
account:write	For Product APIs, the application will be able to update the account data the end user has entitlements to.	authorizationCode, clientCredentials
bucket:create	The application will be able to create an OSS bucket it will own.	clientCredentials
bucket:delete	The application will be able to delete a bucket that it has permission to delete.	clientCredentials
bucket:read	The application will be able to read the metadata and list contents for OSS buckets that it has access to.	clientCredentials
bucket:update	The application will be able to set permissions and entitlements for OSS buckets that it has permission to modify.	clientCredentials
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).	clientCredentials
data:create	The application will be able to create data on behalf of the end user within the Autodesk ecosystem.	authorizationCode, clientCredentials
data:read	The application will be able to read all the end user’s data (viewable and non-viewable) within the Autodesk ecosystem.	authorizationCode, clientCredentials
data:search	The application will be able to search the end user’s data within the Autodesk ecosystem.	authorizationCode, clientCredentials
data:write	The application will be able to create, update, and delete data on behalf of the end user within the Autodesk ecosystem.	authorizationCode, clientCredentials
user-profile:read	The application will be able to read the end user’s profile data (not including associated products and services).	authorizationCode
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.

📄 Provider scope reference: https://aps.autodesk.com/en/docs/oauth/v2/developers_guide/scopes/

Source

OAuth Scopes

generated: '2026-11-11'
method: searched
source: https://developer.doc.autodesk.com/bPlouYTd/cloud-platform-id-pubdocs-master-756267/oauth/v2/developers_guide/scopes.html
schemes:
- name: OAuth2ThreeLegged
  source: openapi/autodesk-acc-account-admin-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://developer.api.autodesk.com/authentication/v2/authorize
    tokenUrl: https://developer.api.autodesk.com/authentication/v2/token
- name: OAuth2TwoLegged
  source: openapi/autodesk-authentication-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://developer.api.autodesk.com/authentication/v2/token
- name: OAuth2ThreeLegged
  source: openapi/autodesk-authentication-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://developer.api.autodesk.com/authentication/v2/authorize
    tokenUrl: https://developer.api.autodesk.com/authentication/v2/token
- name: OAuth2ThreeLegged
  source: openapi/autodesk-bim360-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://developer.api.autodesk.com/authentication/v2/authorize
    tokenUrl: https://developer.api.autodesk.com/authentication/v2/token
- name: OAuth2TwoLegged
  source: openapi/autodesk-data-management-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://developer.api.autodesk.com/authentication/v2/token
- name: OAuth2ThreeLegged
  source: openapi/autodesk-data-management-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://developer.api.autodesk.com/authentication/v2/authorize
    tokenUrl: https://developer.api.autodesk.com/authentication/v2/token
- name: OAuth2TwoLegged
  source: openapi/autodesk-design-automation-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://developer.api.autodesk.com/authentication/v2/token
- name: OAuth2TwoLegged
  source: openapi/autodesk-flow-graph-engine-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://developer.api.autodesk.com/authentication/v2/token
- name: OAuth2TwoLegged
  source: openapi/autodesk-model-derivative-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://developer.api.autodesk.com/authentication/v2/token
- name: OAuth2ThreeLegged
  source: openapi/autodesk-model-derivative-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://developer.api.autodesk.com/authentication/v2/authorize
    tokenUrl: https://developer.api.autodesk.com/authentication/v2/token
- name: OAuth2ThreeLegged
  source: openapi/autodesk-parameters-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://developer.api.autodesk.com/authentication/v2/authorize
    tokenUrl: https://developer.api.autodesk.com/authentication/v2/token
- name: OAuth2TwoLegged
  source: openapi/autodesk-reality-capture-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://developer.api.autodesk.com/authentication/v2/token
- name: OAuth2TwoLegged
  source: openapi/autodesk-sustainability-data-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://developer.api.autodesk.com/authentication/v2/token
- name: OAuth2ThreeLegged
  source: openapi/autodesk-tandem-data-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://developer.api.autodesk.com/authentication/v2/authorize
    tokenUrl: https://developer.api.autodesk.com/authentication/v2/token
- name: OAuth2TwoLegged
  source: openapi/autodesk-webhooks-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://developer.api.autodesk.com/authentication/v2/token
- name: OAuth2ThreeLegged
  source: openapi/autodesk-webhooks-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://developer.api.autodesk.com/authentication/v2/authorize
    tokenUrl: https://developer.api.autodesk.com/authentication/v2/token
scopes:
- scope: account:read
  description: For Product APIs, the application will be able to read the account data the end user has entitlements
    to.
  flows:
  - authorizationCode
  - clientCredentials
  sources:
  - openapi/autodesk-acc-account-admin-openapi.yml
  - openapi/autodesk-authentication-openapi.yml
  - openapi/autodesk-bim360-openapi.yml
  spec_description: Read account data
  consent_message: View your product and service accounts
  documented: true
- scope: account:write
  description: For Product APIs, the application will be able to update the account data the end user has entitlements
    to.
  flows:
  - authorizationCode
  - clientCredentials
  sources:
  - openapi/autodesk-acc-account-admin-openapi.yml
  - openapi/autodesk-authentication-openapi.yml
  - openapi/autodesk-bim360-openapi.yml
  spec_description: Write account data
  consent_message: Manage your product and service accounts
  documented: true
- scope: bucket:create
  description: The application will be able to create an OSS bucket it will own.
  flows:
  - clientCredentials
  sources:
  - openapi/autodesk-authentication-openapi.yml
  - openapi/autodesk-data-management-openapi.yml
  spec_description: Create OSS buckets
  consent_message: Create new buckets
  documented: true
- scope: bucket:delete
  description: The application will be able to delete a bucket that it has permission to delete.
  flows:
  - clientCredentials
  sources:
  - openapi/autodesk-authentication-openapi.yml
  - openapi/autodesk-data-management-openapi.yml
  spec_description: Delete OSS buckets
  consent_message: Delete your buckets
  documented: true
- scope: bucket:read
  description: The application will be able to read the metadata and list contents for OSS buckets that it has access
    to.
  flows:
  - clientCredentials
  sources:
  - openapi/autodesk-authentication-openapi.yml
  - openapi/autodesk-data-management-openapi.yml
  spec_description: Read OSS buckets
  consent_message: View your buckets
  documented: true
- scope: bucket:update
  description: The application will be able to set permissions and entitlements for OSS buckets that it has permission
    to modify.
  flows:
  - clientCredentials
  sources:
  - openapi/autodesk-authentication-openapi.yml
  - openapi/autodesk-data-management-openapi.yml
  spec_description: Update OSS buckets
  consent_message: Update your buckets
  documented: true
- scope: code:all
  description: 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).
  flows:
  - clientCredentials
  sources:
  - openapi/autodesk-authentication-openapi.yml
  - openapi/autodesk-design-automation-openapi.yml
  - openapi/autodesk-flow-graph-engine-openapi.yml
  spec_description: Execute Design Automation activities
  consent_message: Author or execute your codes
  documented: true
- scope: data:create
  description: The application will be able to create data on behalf of the end user within the Autodesk ecosystem.
  flows:
  - authorizationCode
  - clientCredentials
  sources:
  - openapi/autodesk-authentication-openapi.yml
  - openapi/autodesk-data-management-openapi.yml
  - openapi/autodesk-model-derivative-openapi.yml
  - openapi/autodesk-reality-capture-openapi.yml
  spec_description: Create new data
  consent_message: Write data
  documented: true
- scope: data:read
  description: The application will be able to read all the end user’s data (viewable and non-viewable) within the
    Autodesk ecosystem.
  flows:
  - authorizationCode
  - clientCredentials
  sources:
  - openapi/autodesk-authentication-openapi.yml
  - openapi/autodesk-bim360-openapi.yml
  - openapi/autodesk-data-management-openapi.yml
  - openapi/autodesk-model-derivative-openapi.yml
  - openapi/autodesk-parameters-openapi.yml
  - openapi/autodesk-reality-capture-openapi.yml
  - openapi/autodesk-sustainability-data-openapi.yml
  - openapi/autodesk-tandem-data-openapi.yml
  - openapi/autodesk-webhooks-openapi.yml
  spec_description: Read access to data
  consent_message: View your data
  documented: true
- scope: data:search
  description: The application will be able to search the end user’s data within the Autodesk ecosystem.
  flows:
  - authorizationCode
  - clientCredentials
  sources:
  - openapi/autodesk-authentication-openapi.yml
  - openapi/autodesk-data-management-openapi.yml
  spec_description: Search data
  consent_message: Search across your data
  documented: true
- scope: data:write
  description: The application will be able to create, update, and delete data on behalf of the end user within
    the Autodesk ecosystem.
  flows:
  - authorizationCode
  - clientCredentials
  sources:
  - openapi/autodesk-authentication-openapi.yml
  - openapi/autodesk-bim360-openapi.yml
  - openapi/autodesk-data-management-openapi.yml
  - openapi/autodesk-model-derivative-openapi.yml
  - openapi/autodesk-parameters-openapi.yml
  - openapi/autodesk-reality-capture-openapi.yml
  - openapi/autodesk-tandem-data-openapi.yml
  - openapi/autodesk-webhooks-openapi.yml
  spec_description: Write access to data
  consent_message: Manage your data
  documented: true
- scope: user-profile:read
  description: The application will be able to read the end user’s profile data (not including associated products
    and services).
  flows:
  - authorizationCode
  sources:
  - openapi/autodesk-authentication-openapi.yml
  spec_description: Read user profile
  consent_message: View your profile info
  documented: true
- scope: user:read
  description: The application will be able to read the end user’s profile data, including associated products and
    services.
  consent_message: View your profile info
  documented: true
  sources:
  - docs
- scope: user:write
  description: The application will be able to create, update, and delete the end user’s profile data, including
    associated products and services.
  consent_message: Manage your profile info
  documented: true
  sources:
  - docs
- scope: viewables:read
  description: The application will only be able to read the end user’s viewable data (e.g., PNG and SVF files)
    within the Autodesk ecosystem.
  consent_message: View your viewable data
  documented: true
  sources:
  - docs
docs: https://aps.autodesk.com/en/docs/oauth/v2/developers_guide/scopes/
derived_from: openapi/autodesk-acc-account-admin-openapi.yml, openapi/autodesk-authentication-openapi.yml, openapi/autodesk-bim360-openapi.yml,
  openapi/autodesk-data-management-openapi.yml, openapi/autodesk-design-automation-openapi.yml, openapi/autodesk-flow-graph-engine-openapi.yml,
  openapi/autodesk-model-derivative-openapi.yml, openapi/autodesk-parameters-openapi.yml, openapi/autodesk-reality-capture-openapi.yml,
  openapi/autodesk-sustainability-data-openapi.yml, openapi/autodesk-tandem-data-openapi.yml, openapi/autodesk-webhooks-openapi.yml
scope_format: <namespace>:<operation>
docs_notes: Scopes are mandatory for all access tokens; calls without scopes will be rejected.

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.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/autodesk-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?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.