# New Scopes Preventing Authentication

**URL:** <https://community.servicem8.com/t/new-scopes-preventing-authentication/123>\
**Category:** API & SDK\
**Created:** [August 13, 2025, 10:05am UTC](https://community.servicem8.com/t/new-scopes-preventing-authentication/123 "2025-08-13T10:05:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![developer](https://avatars.discourse-cdn.com/v4/letter/d/bcef8e/32.png) [@developer](https://community.servicem8.com/u/developer)\
**Post date:** [August 13, 2025, 10:05am UTC](https://community.servicem8.com/t/new-scopes-preventing-authentication/123/1 "2025-08-13T10:05:16Z")

</div>

**Originally posted by John S**

We’re experiencing issues with our API integration that started this morning. Several of our API requests are now returning a ‘forbidden’ status with an ‘insufficient\_scope’ error, specifically mentioning that ‘unavailable’ scope is required to complete these requests.

These API calls were functioning correctly until today, so we suspect this relates to the new scopes we’ve noticed on your documentation page at [https://developer.servicem8.com/docs/authentication](https://developer.servicem8.com/docs/authentication).

The problematic scopes that are preventing our application from authorising properly include:

read\_feedback  
manage\_feedback  
read\_job\_payments  
manage\_job\_payments  
read\_job\_checklists  
manage\_job\_checklists  
read\_security\_roles  
read\_forms  
manage\_forms  
read\_tax\_rates  
manage\_tax\_rates

Our application cannot authenticate when these new scopes are included in our authorisation request, which means we’re unable to access the information that sits behind these scopes. This is causing significant disruption to our service.

We’d appreciate your urgent assistance in resolving this.