- Write scopes permit updates (e.g. POST, PUT, PATCH requests)
- Read scopes permit reads (e.g. GET requests)
Multiple scopes may be needed in order to perform actions on child resources. For example,
matters/write and documents/write are both needed for adding files to a matter.Requesting scopes
Scopes are requested via thescope parameter (space-delimited) when authorizing with the Authorization Code Grant.
Always include the scope parameter and list every scope your app needs, for example scope=contacts%2Fread%20matters%2Fread%20matters%2Fwrite.
Each requested scope must be assigned to your app in the Developer Console.
The install URL shown on your app’s page in the Developer Console is generated for you.
It includes every scope currently assigned to the app, sorted alphabetically, and changes as you add or remove scopes.
Copy it from the console rather than building it by hand.
If the
scope parameter is omitted, the authorization server currently falls back to issuing a token with all scopes assigned to the app.
OAuth 2.0 expects clients to request their scopes explicitly, so do not rely on this fallback.The Client Credentials Grant does not take a
scope parameter.
Tokens issued by that grant carry every scope assigned to the app in the Developer Console.Scope reference
Matters
Billing & Accounting
Contacts, Firm & Users
Communication & Events
Tasks
Platform & Integration
Plugins are not yet available for partners. They will be supported in a future developer console version, so the
plugins/read and plugins/write scopes cannot be used yet.