generated: '2026-08-13'
method: searched
source: https://www.campaignmonitor.com/api/v3-3/getting-started/
docs: https://www.campaignmonitor.com/api/v3-3/getting-started/
description: >-
  Campaign Monitor calls its OAuth 2.0 scopes "permissions". The complete list is
  published verbatim on the Getting Started page under "Permissions"; there is no
  OpenAPI and no /.well-known/oauth-authorization-server document, so this
  artifact was transcribed from the provider's own reference page rather than
  derived from a spec. Permissions are supplied on the authorize request as a
  single comma-separated `scope` query parameter (URL-encoded, e.g.
  SendCampaigns%2CViewReports).
authorization_url: https://api.createsend.com/oauth
token_url: https://api.createsend.com/oauth/token
delimiter: ","
scope_count: 12
scopes:
  - name: ViewReports
    description: Permission to view reports.
  - name: ManageLists
    description: Permission to manage lists.
  - name: CreateCampaigns
    description: Permission to create campaigns.
  - name: ImportSubscribers
    description: Permission to import subscribers.
  - name: SendCampaigns
    description: Permission to send campaigns.
  - name: ViewSubscribersInReports
    description: Permission to view subscribers in reports.
  - name: ManageTemplates
    description: Permission to manage templates.
  - name: AdministerPersons
    description: Permission to administer persons.
  - name: AdministerAccount
    description: Permission to administer your account.
  - name: ViewTransactional
    description: Permission to view transactional reports and logs.
  - name: SendTransactional
    description: Permission to send transactional email.
  - name: Automation
    description: Permission to view journey reports.
notes:
  - >-
    Scopes are coarse and product-shaped rather than resource/verb-shaped: there
    is no read-only variant of ManageLists or ManageTemplates, so an integration
    that only needs to read lists must still request write permission.
  - >-
    Requesting a permission the API does not recognise fails the OAuth exchange
    with unknown_scope; calling an endpoint outside the granted permissions
    returns HTTP 401 with error code 60.
  - >-
    API-key authentication has no scope surface at all — an API key carries the
    full rights of the account or client it belongs to.
related:
  - authentication/campaignmonitor-authentication.yml