# Confirming API Access to Authoring Limit Site Settings

**URL:** https://meta.discourse.org/t/confirming-api-access-to-authoring-limit-site-settings/407937
**Category:** Development
**Tags:** rest-api
**Created:** [July 18, 2026, 8:21am UTC](https://meta.discourse.org/t/confirming-api-access-to-authoring-limit-site-settings/407937 "2026-07-18T08:21:13Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![philh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/philh/32/532740_2.png) [@philh](https://meta.discourse.org/u/philh)
#### Post date: [July 25, 2026, 11:07pm UTC](https://meta.discourse.org/t/confirming-api-access-to-authoring-limit-site-settings/407937/5 "2026-07-25T23:07:34Z")

</div>

> [@Feature request: Allow safe API access to site settings without an admin-level key](https://meta.discourse.org/t/feature-request-allow-safe-api-access-to-site-settings-without-an-admin-level-key/408523):
>
> As I understand it, requiring admin access for /site/settings.json and some information in /site.json is expected Discourse behavior. Discussion Bridge and similar integrations need a limited set of site configuration information for routine diagnostics, planning, and synchronization. Today this may require using an API key associated with an administrator. A read-only admin key prevents writes, but it can still expose everything the administrator can read. A global admin key carries an unneces…

---

_[View the full topic](https://meta.discourse.org/t/confirming-api-access-to-authoring-limit-site-settings/407937)._