# Welke scope is nodig om toegang te krijgen tot {{localhost}}/posts.json?

**URL:** <https://meta.discourse.org/t/what-scope-is-needed-for-acessing-localhost-posts-json/180358>\
**Category:** Development\
**Created:** [19 februari 2021 om 16:50 UTC](https://meta.discourse.org/t/what-scope-is-needed-for-acessing-localhost-posts-json/180358 "2021-02-19T16:50:03Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)\
**Post date:** [19 februari 2021 om 19:32 UTC](https://meta.discourse.org/t/what-scope-is-needed-for-acessing-localhost-posts-json/180358/2 "2021-02-19T19:32:50Z")

</div>

> [@Hugo\_Tadashi](#):
>
> What is the correct (minimum) scope for reading `{{localhost}}/posts.json` ?

I haven’t tested this yet, but I think that what you are seeing is the expected behaviour. You can click on the anchor button that is displayed next to each of the API key scopes to see which paths the scope allows you to access. You’ll see that the `read` scope is only applied to routes beginning with `/t`. The `read lists` scope gives you access to the Discourse topic lists. There isn’t a scope that specifically allows you to access `/posts.json`, so it looks like you’ll have to use a global key for that.

I’m wondering if it would make sense to add `/posts.json` to the `read` scope.

---

_[View the full topic](https://meta.discourse.org/t/what-scope-is-needed-for-acessing-localhost-posts-json/180358)._
