Acquia · OAuth Scopes

Acquia OAuth Scopes

OAuth 2.0 searched

Acquia publishes 1 OAuth 2.0 scope via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Acquia API on a user’s behalf.

Tokens are issued from https://accounts.acquia.com/api/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.

ContentExperienceDrupalDXPCMSDigital Asset ManagementCloud HostingHeadless
Scopes: 1 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://accounts.acquia.com/api/token
Flows
clientCredentials

Scopes (1)

ScopeDescriptionFlows
organization:{uuid} Grants the API token access to the resources of the organization identified by the given UUID; required when generating an API token for an organization that uses Federated Authentication.

Source

OAuth Scopes

Raw ↑
generated: '2026-08-30'
method: searched
docs:
- https://dev.acquia.com/source-cms/reference/authentication.md
- https://docs.acquia.com/acquia-cloud-platform/cloud-platform-api-v2-authentication
note: 'Acquia runs two OAuth surfaces with completely different scope models. (1) Cloud Platform API:
  OAuth 2.0 client_credentials tied to per-user API tokens, with access governed by Teams and Permissions
  ROLES rather than a scope catalog; the only documented scope is organization:{uuid}, required when the
  organization uses Federated Authentication. That is why the OpenAPI declares 19 oauth2 securitySchemes
  carrying ZERO scopes. (2) Source CMS Content API and MCP server: a real 22-scope vocabulary, selected
  as checkboxes on each API client, published in full at dev.acquia.com. The Source CMS vocabulary is
  recorded below and was NOT present in earlier rounds.'
source: openapi/acquia-cloud-account.yml, openapi/acquia-cloud-agreements.yml, openapi/acquia-cloud-application-performance-monitoring-services.yml,
  openapi/acquia-cloud-applications.yml, openapi/acquia-cloud-cloud-ide.yml, openapi/acquia-cloud-codebases.yml,
  openapi/acquia-cloud-current-system-health.yml, openapi/acquia-cloud-distributions.yml, openapi/acquia-cloud-email.yml,
  openapi/acquia-cloud-environments.yml, openapi/acquia-cloud-identity-providers.yml, openapi/acquia-cloud-invite.yml,
  openapi/acquia-cloud-messages.yml, openapi/acquia-cloud-notifications.yml, openapi/acquia-cloud-openapi-full.yml,
  openapi/acquia-cloud-options.yml, openapi/acquia-cloud-organizations.yml, openapi/acquia-cloud-private-networks.yml,
  openapi/acquia-cloud-subscriptions.yml, openapi/acquia-cloud-teams-and-permissions.yml
schemes:
- name: Acquia_Cloud_API_Documentation_OAuth2
  source: openapi/acquia-cloud-account.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://accounts.acquia.com/api/token
  description: 'All Cloud API calls need to be authenticated in order to work. You authenticate using
    a token that you can generate on your Acquia Profile page.


    ### To generate a token:


    1. Sign in to the [Acquia Cloud](https://cloud.acquia.com/) interface using your email address and
    Acquia password.

    2. Click your user avatar in the upper right corner, and then click **Account Settings**.

    3. On the Profile page, click **API Tokens**.

    4. Click **Create Token**.

    5. In the pop-up that appears, give your token a label so that you can easily find it later. Then
    click **Create Token**.

    6. Copy your API key and API secret. Click **OK**.'
- name: Acquia_Cloud_API_Documentation_OAuth2
  source: openapi/acquia-cloud-agreements.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://accounts.acquia.com/api/token
  description: 'All Cloud API calls need to be authenticated in order to work. You authenticate using
    a token that you can generate on your Acquia Profile page.


    ### To generate a token:


    1. Sign in to the [Acquia Cloud](https://cloud.acquia.com/) interface using your email address and
    Acquia password.

    2. Click your user avatar in the upper right corner, and then click **Account Settings**.

    3. On the Profile page, click **API Tokens**.

    4. Click **Create Token**.

    5. In the pop-up that appears, give your token a label so that you can easily find it later. Then
    click **Create Token**.

    6. Copy your API key and API secret. Click **OK**.'
- name: Acquia_Cloud_API_Documentation_OAuth2
  source: openapi/acquia-cloud-application-performance-monitoring-services.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://accounts.acquia.com/api/token
  description: 'All Cloud API calls need to be authenticated in order to work. You authenticate using
    a token that you can generate on your Acquia Profile page.


    ### To generate a token:


    1. Sign in to the [Acquia Cloud](https://cloud.acquia.com/) interface using your email address and
    Acquia password.

    2. Click your user avatar in the upper right corner, and then click **Account Settings**.

    3. On the Profile page, click **API Tokens**.

    4. Click **Create Token**.

    5. In the pop-up that appears, give your token a label so that you can easily find it later. Then
    click **Create Token**.

    6. Copy your API key and API secret. Click **OK**.'
- name: Acquia_Cloud_API_Documentation_OAuth2
  source: openapi/acquia-cloud-applications.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://accounts.acquia.com/api/token
  description: 'All Cloud API calls need to be authenticated in order to work. You authenticate using
    a token that you can generate on your Acquia Profile page.


    ### To generate a token:


    1. Sign in to the [Acquia Cloud](https://cloud.acquia.com/) interface using your email address and
    Acquia password.

    2. Click your user avatar in the upper right corner, and then click **Account Settings**.

    3. On the Profile page, click **API Tokens**.

    4. Click **Create Token**.

    5. In the pop-up that appears, give your token a label so that you can easily find it later. Then
    click **Create Token**.

    6. Copy your API key and API secret. Click **OK**.'
- name: Acquia_Cloud_API_Documentation_OAuth2
  source: openapi/acquia-cloud-cloud-ide.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://accounts.acquia.com/api/token
  description: 'All Cloud API calls need to be authenticated in order to work. You authenticate using
    a token that you can generate on your Acquia Profile page.


    ### To generate a token:


    1. Sign in to the [Acquia Cloud](https://cloud.acquia.com/) interface using your email address and
    Acquia password.

    2. Click your user avatar in the upper right corner, and then click **Account Settings**.

    3. On the Profile page, click **API Tokens**.

    4. Click **Create Token**.

    5. In the pop-up that appears, give your token a label so that you can easily find it later. Then
    click **Create Token**.

    6. Copy your API key and API secret. Click **OK**.'
- name: Acquia_Cloud_API_Documentation_OAuth2
  source: openapi/acquia-cloud-codebases.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://accounts.acquia.com/api/token
  description: 'All Cloud API calls need to be authenticated in order to work. You authenticate using
    a token that you can generate on your Acquia Profile page.


    ### To generate a token:


    1. Sign in to the [Acquia Cloud](https://cloud.acquia.com/) interface using your email address and
    Acquia password.

    2. Click your user avatar in the upper right corner, and then click **Account Settings**.

    3. On the Profile page, click **API Tokens**.

    4. Click **Create Token**.

    5. In the pop-up that appears, give your token a label so that you can easily find it later. Then
    click **Create Token**.

    6. Copy your API key and API secret. Click **OK**.'
- name: Acquia_Cloud_API_Documentation_OAuth2
  source: openapi/acquia-cloud-current-system-health.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://accounts.acquia.com/api/token
  description: 'All Cloud API calls need to be authenticated in order to work. You authenticate using
    a token that you can generate on your Acquia Profile page.


    ### To generate a token:


    1. Sign in to the [Acquia Cloud](https://cloud.acquia.com/) interface using your email address and
    Acquia password.

    2. Click your user avatar in the upper right corner, and then click **Account Settings**.

    3. On the Profile page, click **API Tokens**.

    4. Click **Create Token**.

    5. In the pop-up that appears, give your token a label so that you can easily find it later. Then
    click **Create Token**.

    6. Copy your API key and API secret. Click **OK**.'
- name: Acquia_Cloud_API_Documentation_OAuth2
  source: openapi/acquia-cloud-distributions.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://accounts.acquia.com/api/token
  description: 'All Cloud API calls need to be authenticated in order to work. You authenticate using
    a token that you can generate on your Acquia Profile page.


    ### To generate a token:


    1. Sign in to the [Acquia Cloud](https://cloud.acquia.com/) interface using your email address and
    Acquia password.

    2. Click your user avatar in the upper right corner, and then click **Account Settings**.

    3. On the Profile page, click **API Tokens**.

    4. Click **Create Token**.

    5. In the pop-up that appears, give your token a label so that you can easily find it later. Then
    click **Create Token**.

    6. Copy your API key and API secret. Click **OK**.'
- name: Acquia_Cloud_API_Documentation_OAuth2
  source: openapi/acquia-cloud-email.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://accounts.acquia.com/api/token
  description: 'All Cloud API calls need to be authenticated in order to work. You authenticate using
    a token that you can generate on your Acquia Profile page.


    ### To generate a token:


    1. Sign in to the [Acquia Cloud](https://cloud.acquia.com/) interface using your email address and
    Acquia password.

    2. Click your user avatar in the upper right corner, and then click **Account Settings**.

    3. On the Profile page, click **API Tokens**.

    4. Click **Create Token**.

    5. In the pop-up that appears, give your token a label so that you can easily find it later. Then
    click **Create Token**.

    6. Copy your API key and API secret. Click **OK**.'
- name: Acquia_Cloud_API_Documentation_OAuth2
  source: openapi/acquia-cloud-environments.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://accounts.acquia.com/api/token
  description: 'All Cloud API calls need to be authenticated in order to work. You authenticate using
    a token that you can generate on your Acquia Profile page.


    ### To generate a token:


    1. Sign in to the [Acquia Cloud](https://cloud.acquia.com/) interface using your email address and
    Acquia password.

    2. Click your user avatar in the upper right corner, and then click **Account Settings**.

    3. On the Profile page, click **API Tokens**.

    4. Click **Create Token**.

    5. In the pop-up that appears, give your token a label so that you can easily find it later. Then
    click **Create Token**.

    6. Copy your API key and API secret. Click **OK**.'
- name: Acquia_Cloud_API_Documentation_OAuth2
  source: openapi/acquia-cloud-identity-providers.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://accounts.acquia.com/api/token
  description: 'All Cloud API calls need to be authenticated in order to work. You authenticate using
    a token that you can generate on your Acquia Profile page.


    ### To generate a token:


    1. Sign in to the [Acquia Cloud](https://cloud.acquia.com/) interface using your email address and
    Acquia password.

    2. Click your user avatar in the upper right corner, and then click **Account Settings**.

    3. On the Profile page, click **API Tokens**.

    4. Click **Create Token**.

    5. In the pop-up that appears, give your token a label so that you can easily find it later. Then
    click **Create Token**.

    6. Copy your API key and API secret. Click **OK**.'
- name: Acquia_Cloud_API_Documentation_OAuth2
  source: openapi/acquia-cloud-invite.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://accounts.acquia.com/api/token
  description: 'All Cloud API calls need to be authenticated in order to work. You authenticate using
    a token that you can generate on your Acquia Profile page.


    ### To generate a token:


    1. Sign in to the [Acquia Cloud](https://cloud.acquia.com/) interface using your email address and
    Acquia password.

    2. Click your user avatar in the upper right corner, and then click **Account Settings**.

    3. On the Profile page, click **API Tokens**.

    4. Click **Create Token**.

    5. In the pop-up that appears, give your token a label so that you can easily find it later. Then
    click **Create Token**.

    6. Copy your API key and API secret. Click **OK**.'
- name: Acquia_Cloud_API_Documentation_OAuth2
  source: openapi/acquia-cloud-messages.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://accounts.acquia.com/api/token
  description: 'All Cloud API calls need to be authenticated in order to work. You authenticate using
    a token that you can generate on your Acquia Profile page.


    ### To generate a token:


    1. Sign in to the [Acquia Cloud](https://cloud.acquia.com/) interface using your email address and
    Acquia password.

    2. Click your user avatar in the upper right corner, and then click **Account Settings**.

    3. On the Profile page, click **API Tokens**.

    4. Click **Create Token**.

    5. In the pop-up that appears, give your token a label so that you can easily find it later. Then
    click **Create Token**.

    6. Copy your API key and API secret. Click **OK**.'
- name: Acquia_Cloud_API_Documentation_OAuth2
  source: openapi/acquia-cloud-notifications.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://accounts.acquia.com/api/token
  description: 'All Cloud API calls need to be authenticated in order to work. You authenticate using
    a token that you can generate on your Acquia Profile page.


    ### To generate a token:


    1. Sign in to the [Acquia Cloud](https://cloud.acquia.com/) interface using your email address and
    Acquia password.

    2. Click your user avatar in the upper right corner, and then click **Account Settings**.

    3. On the Profile page, click **API Tokens**.

    4. Click **Create Token**.

    5. In the pop-up that appears, give your token a label so that you can easily find it later. Then
    click **Create Token**.

    6. Copy your API key and API secret. Click **OK**.'
- name: Acquia_Cloud_API_Documentation_OAuth2
  source: openapi/acquia-cloud-openapi-full.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://accounts.acquia.com/api/token
  description: 'All Cloud API calls need to be authenticated in order to work. You authenticate using
    a token that you can generate on your Acquia Profile page.


    ### To generate a token:


    1. Sign in to the [Acquia Cloud](https://cloud.acquia.com/) interface using your email address and
    Acquia password.

    2. Click your user avatar in the upper right corner, and then click **Account Settings**.

    3. On the Profile page, click **API Tokens**.

    4. Click **Create Token**.

    5. In the pop-up that appears, give your token a label so that you can easily find it later. Then
    click **Create Token**.

    6. Copy your API key and API secret. Click **OK**.'
- name: Acquia_Cloud_API_Documentation_OAuth2
  source: openapi/acquia-cloud-options.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://accounts.acquia.com/api/token
  description: 'All Cloud API calls need to be authenticated in order to work. You authenticate using
    a token that you can generate on your Acquia Profile page.


    ### To generate a token:


    1. Sign in to the [Acquia Cloud](https://cloud.acquia.com/) interface using your email address and
    Acquia password.

    2. Click your user avatar in the upper right corner, and then click **Account Settings**.

    3. On the Profile page, click **API Tokens**.

    4. Click **Create Token**.

    5. In the pop-up that appears, give your token a label so that you can easily find it later. Then
    click **Create Token**.

    6. Copy your API key and API secret. Click **OK**.'
- name: Acquia_Cloud_API_Documentation_OAuth2
  source: openapi/acquia-cloud-organizations.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://accounts.acquia.com/api/token
  description: 'All Cloud API calls need to be authenticated in order to work. You authenticate using
    a token that you can generate on your Acquia Profile page.


    ### To generate a token:


    1. Sign in to the [Acquia Cloud](https://cloud.acquia.com/) interface using your email address and
    Acquia password.

    2. Click your user avatar in the upper right corner, and then click **Account Settings**.

    3. On the Profile page, click **API Tokens**.

    4. Click **Create Token**.

    5. In the pop-up that appears, give your token a label so that you can easily find it later. Then
    click **Create Token**.

    6. Copy your API key and API secret. Click **OK**.'
- name: Acquia_Cloud_API_Documentation_OAuth2
  source: openapi/acquia-cloud-private-networks.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://accounts.acquia.com/api/token
  description: 'All Cloud API calls need to be authenticated in order to work. You authenticate using
    a token that you can generate on your Acquia Profile page.


    ### To generate a token:


    1. Sign in to the [Acquia Cloud](https://cloud.acquia.com/) interface using your email address and
    Acquia password.

    2. Click your user avatar in the upper right corner, and then click **Account Settings**.

    3. On the Profile page, click **API Tokens**.

    4. Click **Create Token**.

    5. In the pop-up that appears, give your token a label so that you can easily find it later. Then
    click **Create Token**.

    6. Copy your API key and API secret. Click **OK**.'
- name: Acquia_Cloud_API_Documentation_OAuth2
  source: openapi/acquia-cloud-subscriptions.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://accounts.acquia.com/api/token
  description: 'All Cloud API calls need to be authenticated in order to work. You authenticate using
    a token that you can generate on your Acquia Profile page.


    ### To generate a token:


    1. Sign in to the [Acquia Cloud](https://cloud.acquia.com/) interface using your email address and
    Acquia password.

    2. Click your user avatar in the upper right corner, and then click **Account Settings**.

    3. On the Profile page, click **API Tokens**.

    4. Click **Create Token**.

    5. In the pop-up that appears, give your token a label so that you can easily find it later. Then
    click **Create Token**.

    6. Copy your API key and API secret. Click **OK**.'
- name: Acquia_Cloud_API_Documentation_OAuth2
  source: openapi/acquia-cloud-teams-and-permissions.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://accounts.acquia.com/api/token
  description: 'All Cloud API calls need to be authenticated in order to work. You authenticate using
    a token that you can generate on your Acquia Profile page.


    ### To generate a token:


    1. Sign in to the [Acquia Cloud](https://cloud.acquia.com/) interface using your email address and
    Acquia password.

    2. Click your user avatar in the upper right corner, and then click **Account Settings**.

    3. On the Profile page, click **API Tokens**.

    4. Click **Create Token**.

    5. In the pop-up that appears, give your token a label so that you can easily find it later. Then
    click **Create Token**.

    6. Copy your API key and API secret. Click **OK**.'
scopes:
- scope: organization:{uuid}
  description: Grants the API token access to the resources of the organization identified by the given
    UUID; required when generating an API token for an organization that uses Federated Authentication.
  sources:
  - https://docs.acquia.com/acquia-cloud-platform/cloud-platform-api-v2-authentication
surfaces:
- name: Cloud Platform API
  scope_model: role-based (Teams and Permissions), not scope-based
  scope_count: 1
  tokenUrl: https://accounts.acquia.com/api/token
  scopes:
  - name: organization:{uuid}
    description: Required when the organization uses Federated Authentication.
    source: https://docs.acquia.com/acquia-cloud-platform/cloud-platform-api-v2-authentication
- name: Source CMS (Content API + MCP server)
  scope_model: scope-based, selected per API client at API > API clients
  scope_count: 22
  tokenUrl: '{DRUPAL_SITE_URL}/oauth/token'
  source: https://dev.acquia.com/source-cms/reference/authentication.md
  defaulting: A token request with NO scope parameter carries every scope selected on the client. A scope
    parameter may only narrow to a subset; naming an unknown or unselected scope returns a 400 invalid_scope
    whose hint names the offending scope.
  gating_note: 'Scopes gate writes and admin surfaces, not published-content reads: a GET for published
    content succeeds with any valid token regardless of scope, and with no token at all when the site''s
    Public access setting is Yes. Reading UNPUBLISHED content requires content:administer.'
  mcp_note: 'Acquia''s MCP reference reports 16 scopes_supported in the MCP resource-metadata document
    - a subset of the 22 below - and records that scope gating was NOT observable in its own verification:
    a client_credentials token issued without a scope parameter called every tool successfully.'
  scopes:
  - name: content:administer
    description: 'Content CRUD over JSON:API: create, update and delete entries. There is no read-only
      content scope.'
  - name: content_type:administer
    description: Content types (bundles).
  - name: content_type:administer_fields
    description: Fields on content types.
  - name: page_template:administer
    description: Page templates.
  - name: media:administer
    description: Media entries.
  - name: media_type:administer
    description: Media types.
  - name: taxonomy:administer
    description: Taxonomy vocabularies and terms.
  - name: taxonomy:administer_fields
    description: Fields on taxonomy terms.
  - name: menu:administer
    description: Menus.
  - name: site_settings:administer
    description: Site settings.
  - name: canvas:page:read
    description: Read Canvas pages.
  - name: canvas:page:create
    description: Create Canvas pages.
  - name: canvas:page:edit
    description: Edit Canvas pages.
  - name: canvas:page:delete
    description: Delete Canvas pages.
  - name: canvas:page_region
    description: Canvas page regions.
  - name: canvas:content_template
    description: Canvas content templates.
  - name: canvas:asset_library
    description: 'Drupal Canvas CLI: asset library access for downloading and uploading components.'
  - name: canvas:js_component
    description: 'Drupal Canvas CLI: JS component access for downloading and uploading components.'
  - name: canvas:brand_kit
    description: Canvas brand kits.
  - name: canvas:media:view
    description: View media from Canvas.
  - name: canvas:media:image:create
    description: Create images from Canvas.
  - name: member
    description: Basic member access.
scope_count: 23

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/acquia-scopes"
All oauth scopes
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.

A second provider on the same verified email joins the account you already have.