# Docs:read:export:admin scope added but missing from issued Server-to-Server OAuth access token

**URL:** <https://devforum.zoom.us/t/docsexport-admin-scope-added-but-missing-from-issued-server-to-server-oauth-access-token/146162>\
**Category:** Users and Groups\
**Tags:** api\
**Created:** [September 3, 2026, 2:57am UTC](https://devforum.zoom.us/t/docsexport-admin-scope-added-but-missing-from-issued-server-to-server-oauth-access-token/146162 "2026-09-03T02:57:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mish](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/mish/32/49100_2.png) [@mish](https://devforum.zoom.us/u/mish)\
**Post date:** [September 3, 2026, 2:57am UTC](https://devforum.zoom.us/t/docsexport-admin-scope-added-but-missing-from-issued-server-to-server-oauth-access-token/146162/1 "2026-09-03T02:57:30Z")

</div>

## API Endpoint(s) and/or Zoom API Event(s)

- GET /v2/docs/files/{fileId}/content (Zoom Docs Export API, released 2026-03-30)
- POST /v2/oauth/token (Server-to-Server OAuth, grant\_type=account\_credentials)

## Description

I have a Server-to-Server OAuth app and want to call the Zoom Docs Export API to  
retrieve the content of an AI Companion meeting summary doc. I added the scope  
`docs:read:export:admin` in the app’s Scopes tab (it shows as added/checked), but  
the access token issued via the account\_credentials grant does not include this  
scope at all — confirmed by decoding the JWT “scope” claim, no “docs” scope appears.

Other scopes on the same app (cloud\_recording:read:meeting\_transcript:admin,  
cloud\_recording:read:list\_user\_recordings:admin, cloud\_recording:read:recording:admin,  
meeting:read:summary:admin) work correctly and do appear in the issued token.

I’ve already tried deactivating and reactivating the app after adding the scope, but  
the issue persists.

## Error?

401 Unauthorized

{ “code”:104, “message”:“Invalid access token, does not contain scopes:[docs:read:export]” }

## How To Reproduce

1. Request:  
Method: GET  
Path: /v2/docs/files/{fileId}/content (Zoom REST API base URL)  
Headers: Authorization: Bearer {a  
Body: none

2. Authentication method: Server-to-Server OAuth (account\_credentials grant),  
app type “Account-level app”

3. Steps:

Is `docs:read:export:admin` / the Zoehind an  
account-level entitlement (plan or feature flag) separate from the app’s scope  
configuration? If so, how can that b

---

<div class="post-metadata">

**Author:** ![amanda-recallai](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amanda-recallai/32/44747_2.png) [@amanda-recallai](https://devforum.zoom.us/u/amanda-recallai)\
**Post date:** [September 3, 2026, 4:32pm UTC](https://devforum.zoom.us/t/docsexport-admin-scope-added-but-missing-from-issued-server-to-server-oauth-access-token/146162/2 "2026-09-03T16:32:31Z")

</div>

This specific 104 error points to an app-type and scope mismatch. A Zoom engineer confirmed in a [near-identical S2S case](https://devforum.zoom.us/t/zoom-docs-export-endpoint-rejects-admin-scope-variant-on-s2s-oauth-apps/143114/3) that this endpoint does not work with Server-to-Server OAuth because S2S has no associated compatible scope. Instead create a [General App](https://developers.zoom.us/docs/integrations/create/) and use Zoom’s [authorization-code OAuth flow](https://developers.zoom.us/docs/integrations/oauth/). The clearest supported path is a user-managed app with docs:read:export authorized by the document owner. For account-wide unattended access, use an admin-managed General App or request explicit S2S support from Zoom, since there is no documented feature flag that enables this endpoint for account\_credentials tokens.

For an alternative way to capture and process meeting content, Recall.ai’s [Meeting Bot API](https://www.recall.ai/product/meeting-bot-api?utm_source=zoom&utm_medium=forum_answer) handles the meeting ingestion layer.
