# DISPUTES\_READ scope error when authenticating or fetching from the disputes endpoint

**URL:** <https://developer.squareup.com/forums/t/disputes-read-scope-error-when-authenticating-or-fetching-from-the-disputes-endpoint/2309>\
**Category:** Questions\
**Tags:** disputes-api\
**Created:** [April 14, 2021, 3:13pm UTC](https://developer.squareup.com/forums/t/disputes-read-scope-error-when-authenticating-or-fetching-from-the-disputes-endpoint/2309 "2021-04-14T15:13:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kalpesh](https://avatars.discourse-cdn.com/v4/letter/k/7ba0ec/32.png) [@Kalpesh](https://developer.squareup.com/forums/u/Kalpesh)\
**Post date:** [April 14, 2021, 3:13pm UTC](https://developer.squareup.com/forums/t/disputes-read-scope-error-when-authenticating-or-fetching-from-the-disputes-endpoint/2309/1 "2021-04-14T15:13:23Z")

</div>

Hello since around yesterday I have been getting an error when fetching data from the `v2/disputes` endpoint in the sandbox. The error that has come back is the following:

```auto
{"errors": [{"code": "INSUFFICIENT_SCOPES","detail": "The merchant has not given your application sufficient permissions to do that. The merchant must authorize your application for the following scopes: [DISPUTES_READ]","category": "AUTHENTICATION_ERROR"}]}

```

The scope DISPUTES\_READ is not documented [here](https://developer.squareup.com/docs/oauth-api/square-permissions). When I test it for a prod account it seems to work fine. I am using Api Version `2021-03-17`.

---

<div class="post-metadata">

**Author:** ![sjosey](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/sjosey/32/40_2.png) [@sjosey](https://developer.squareup.com/forums/u/sjosey)\
**Post date:** [April 14, 2021, 5:50pm UTC](https://developer.squareup.com/forums/t/disputes-read-scope-error-when-authenticating-or-fetching-from-the-disputes-endpoint/2309/2 "2021-04-14T17:50:08Z")

</div>

Hi @Kalpesh welcome to the forums!

Seems there was a change on our side, but it has now been fixed. Thanks for reporting!