# Full scope required for review links in developer token

**URL:** <https://forum.frame.io/t/full-scope-required-for-review-links-in-developer-token/496>\
**Category:** Help\
**Tags:** python, review-links\
**Created:** [March 15, 2023, 8:16pm UTC](https://forum.frame.io/t/full-scope-required-for-review-links-in-developer-token/496 "2023-03-15T20:16:35Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![arcmedia](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@arcmedia](https://forum.frame.io/u/arcmedia)\
**Post date:** [March 15, 2023, 8:16pm UTC](https://forum.frame.io/t/full-scope-required-for-review-links-in-developer-token/496/1 "2023-03-15T20:16:35Z")

</div>

What is the full scope required for listing review links (ie, project.review\_links.list([ProjectID])? I have ‘read’ set for review links and for most everything else. I can iterate down from the account level to the project level just fine, but I get a ‘403 Forbidden’ error when I attempt to list the review links with the desired project ID. I also attempted in an http call and received the same error.

Appreciate the help.

---

<div class="post-metadata">

**Author:** ![jhodges](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.frame.io/jhodges/32/3_2.png) [@jhodges](https://forum.frame.io/u/jhodges)\
**Post date:** [March 16, 2023, 5:48pm UTC](https://forum.frame.io/t/full-scope-required-for-review-links-in-developer-token/496/2 "2023-03-16T17:48:26Z")

</div>

Hey there @arcmedia, I just did a quick test based on what you had described and it looks you just need to make sure you have the following scopes so you can do your account traversal before you get to the review links endpoint:

- `account.read`
- `project.read`
- `reviewlink.read`
- `team.read`

If you don’t have access to the project you’re trying to get review links for in our user interface, you won’t be able to list those review links via the API.

---

<div class="post-metadata">

**Author:** ![arcmedia](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@arcmedia](https://forum.frame.io/u/arcmedia)\
**Post date:** [March 17, 2023, 2:36pm UTC](https://forum.frame.io/t/full-scope-required-for-review-links-in-developer-token/496/3 "2023-03-17T14:36:03Z")

</div>

Understood. Turned out to be a permission issue with the user itself the token was assigned to.

---

<div class="post-metadata">

**Author:** ![jhodges](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.frame.io/jhodges/32/3_2.png) [@jhodges](https://forum.frame.io/u/jhodges)\
**Post date:** [March 17, 2023, 6:01pm UTC](https://forum.frame.io/t/full-scope-required-for-review-links-in-developer-token/496/4 "2023-03-17T18:01:30Z")

</div>

Ahh, glad you were able to figure it out!

---

<div class="post-metadata">

**Author:** ![rodferrior](https://avatars.discourse-cdn.com/v4/letter/r/ec9cab/32.png) [@rodferrior](https://forum.frame.io/u/rodferrior)\
**Post date:** [October 19, 2024, 1:00pm UTC](https://forum.frame.io/t/full-scope-required-for-review-links-in-developer-token/496/6 "2024-10-19T13:00:57Z")

</div>

> [@arcmedia](#):
>
> What is the full scope required for listing review links (ie, project.review\_links[.](https://gameroom777.download/)list([ProjectID])? I have ‘read’ set for review links and for most everything else. I can iterate down from the account level to the project level just fine, but I get a ‘403 Forbidden’ error when I attempt to list the review links with the desired project ID. I also attempted in an http call and received the same error.

What additional permissions or scope are required to successfully list review links using project.review\_links.list([ProjectID]) in order to avoid the ‘403 Forbidden’ error?

---

<div class="post-metadata">

**Author:** ![arcmedia](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@arcmedia](https://forum.frame.io/u/arcmedia)\
**Post date:** [October 19, 2024, 4:46pm UTC](https://forum.frame.io/t/full-scope-required-for-review-links-in-developer-token/496/7 "2024-10-19T16:46:59Z")

</div>

The user that the token was created with needs the scope outlined above plus access to both the team and the project (if project is set to private)
