Skip to main content

OAuth 2.0 Scopes

This document provides a comprehensive listing of OAuth 2.0 scopes required to access API endpoints and webhook events.

Key Information

The scope table organizes access permissions across multiple feature areas including:
  • Business Management: businesses (read/write)
  • Calendar Operations: calendars, groups, resources, and events (read/write)
  • Contact Management: contacts with tasks, notes, and campaign associations
  • Conversations: messaging, recordings, and transcriptions
  • Financial: invoices, payments, subscriptions, and transactions
  • Marketing: campaigns, forms, workflows, and social media posting
  • Content: blogs, courses, emails, and surveys
  • Administrative: users, locations, and custom fields/values

Access Types

The scopes are designated for two primary access levels:
  • Sub-Account: Standard operational access for account users
  • Agency: Administrative access for agency-level management
The scopes specify which endpoints require read (readonly) versus write permissions, and list associated webhook events where applicable. Each scope grants access to specific HTTP methods (GET, POST, PUT, DELETE, PATCH) on designated endpoints.

Scope Format

Scopes follow the format:
resource/action.permission
For example:
conversations/message.readonly
conversations/message.write
When building your authorization URL, separate multiple scopes with spaces:
scope=conversations/message.readonly contacts.readonly calendars.write
Last modified on March 4, 2026