# Zoom error %HTTPoison.Response{status\_code: 401, body: "{\\"code\\":104, \\"message\\":\\"Invalid access token, does not contain scopes:\[\\"whiteboard:write\\"\]\\"}" **URL:** \ **Category:** API and Webhooks\ **Tags:** api\ **Created:** [February 27, 2024, 5:26am UTC](https://devforum.zoom.us/t/zoom-error-httpoison-response-status-code-401-body-code-104-message-invalid-access-token-does-not-contain-scopes-whiteboard-write/104585 "2024-02-27T05:26:46Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![tispratik](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tispratik/32/57007_2.png) [@tispratik](https://devforum.zoom.us/u/tispratik)\ **Post date:** [February 27, 2024, 5:26am UTC](https://devforum.zoom.us/t/zoom-error-httpoison-response-status-code-401-body-code-104-message-invalid-access-token-does-not-contain-scopes-whiteboard-write/104585/1 "2024-02-27T05:26:46Z")
We are facing the same issue as mentioned in [Api v2/whiteboards throwing 401 Unauthorized "Invalid access token, does not contain scopes:["whiteboard:write"]"](https://devforum.zoom.us/t/api-v2-whiteboards-throwing-401-unauthorized-invalid-access-token-does-not-contain-scopes-whiteboard-write/98233) But commenting in above issue is turned off. The Whiteboard feature is enabled on our account. ---
**Author:** ![joshua.allen](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/joshua.allen/32/51545_2.png) [@joshua.allen](https://devforum.zoom.us/u/joshua.allen)\ **Post date:** [February 27, 2024, 4:02pm UTC](https://devforum.zoom.us/t/zoom-error-httpoison-response-status-code-401-body-code-104-message-invalid-access-token-does-not-contain-scopes-whiteboard-write/104585/2 "2024-02-27T16:02:10Z")
Are you also using a server to server authentication method? ---
**Author:** ![tispratik](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tispratik/32/57007_2.png) [@tispratik](https://devforum.zoom.us/u/tispratik)\ **Post date:** [February 27, 2024, 4:42pm UTC](https://devforum.zoom.us/t/zoom-error-httpoison-response-status-code-401-body-code-104-message-invalid-access-token-does-not-contain-scopes-whiteboard-write/104585/3 "2024-02-27T16:42:46Z")
Yes we’re using the server to server authentication. Also the feature is correctly enabled in Zoom dashboard. ---
**Author:** ![joshua.allen](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/joshua.allen/32/51545_2.png) [@joshua.allen](https://devforum.zoom.us/u/joshua.allen)\ **Post date:** [February 27, 2024, 5:19pm UTC](https://devforum.zoom.us/t/zoom-error-httpoison-response-status-code-401-body-code-104-message-invalid-access-token-does-not-contain-scopes-whiteboard-write/104585/4 "2024-02-27T17:19:39Z")
When you generate the access token, it should return with the scopes which that token enables you to access, like so. { “access\_token”: “{access\_token}”, “token\_type”: “bearer”, “expires\_in”: 3599, **“scope” : “user:read:admin”** } do you see “writeboard:write” in those scopes? ---
**Author:** ![tispratik](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tispratik/32/57007_2.png) [@tispratik](https://devforum.zoom.us/u/tispratik)\ **Post date:** [March 1, 2024, 5:19am UTC](https://devforum.zoom.us/t/zoom-error-httpoison-response-status-code-401-body-code-104-message-invalid-access-token-does-not-contain-scopes-whiteboard-write/104585/5 "2024-03-01T05:19:18Z")
Hello Josh, Thank you for your help. Please find the response below: { “access\_token”: “xyz”, “token\_type”: “bearer”, “expires\_in”: 3600, “scope”: “user:write:admin meeting\_token:read:admin:local\_recording user:read:admin meeting:read:admin:sip\_dialing information\_barriers:write:admin recording:write:admin whiteboard:read:admin whiteboard\_content:read:admin user:master information\_barriers:read:admin whiteboard\_share\_setting:write:admin meeting:read:admin information\_barriers:read:master recording:read:admin meeting:write:admin meeting\_token:read:admin:live\_streaming meeting:write:admin:sip\_dialing recording:master whiteboard:write:admin meeting:master meeting\_token:read:admin:local\_archiving whiteboard\_export:write:admin whiteboard\_collaborator:write:admin whiteboard\_collaborator:read:admin information\_barriers:write:master” } ---
**Author:** ![joshua.allen](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/joshua.allen/32/51545_2.png) [@joshua.allen](https://devforum.zoom.us/u/joshua.allen)\ **Post date:** [March 6, 2024, 5:31pm UTC](https://devforum.zoom.us/t/zoom-error-httpoison-response-status-code-401-body-code-104-message-invalid-access-token-does-not-contain-scopes-whiteboard-write/104585/6 "2024-03-06T17:31:13Z")
Hmm, well I see ‘whiteboard:write:admin’ in there. That’s weird. Hate to ask the obvious question, but just in case, are you sure that when you’re making the call to the endpoint you’re using the most recent access token, not an old one that maybe didn’t have the scope? ---
**Author:** ![tispratik](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tispratik/32/57007_2.png) [@tispratik](https://devforum.zoom.us/u/tispratik)\ **Post date:** [March 7, 2024, 4:07am UTC](https://devforum.zoom.us/t/zoom-error-httpoison-response-status-code-401-body-code-104-message-invalid-access-token-does-not-contain-scopes-whiteboard-write/104585/7 "2024-03-07T04:07:10Z")
Hello Josh, Thank you for your reply. Yes that is correct, we’re using the latest token. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\ **Post date:** [March 10, 2025, 7:43pm UTC](https://devforum.zoom.us/t/zoom-error-httpoison-response-status-code-401-body-code-104-message-invalid-access-token-does-not-contain-scopes-whiteboard-write/104585/8 "2025-03-10T19:43:52Z")
Closed on March 10, 2025, 7:43pm UTC This topic was automatically closed 368 days after the last reply. New replies are no longer allowed.