Sending text message via API works for my account, but not others

Phone
1

I’m able to successfully send a text message through the ‘v2/phone/sms/messages’ endpoint for my account, but when I try to do the same for someone else in our company, it gives me a 124 error code. Details below. I am a super admin and have all of the scopes on our Server to Server OAuth only app.

Successful response (for my account):
([zoom_trackingid] => WEB_02b63a33165ffd04b0d0d1105dcad503)
----------------------------------------------------------------------------------------------------- {“session_id”:“d0e4b4ca1e1ae9d71ccae95ed8688aeb”,“message_id”:“5595e504-0fc4-41e2-a369-75bd63097ffe”,“date_time”:“2025-05-21T19:14:04Z”}

Unsuccessful (for any other team member’s account)
[zoom_trackingid] => WEB_bd7e543a8470493c99a8104ba5586f33
----------------------------------------------------------------------------------------------------- {“code”:124,“message”:“Invalid access token.”}

I submitted a support ticket Number TS1838509 for this per our discussion during office hours @gianni.zoom

1 Like
3

Thanks so much for joining today and sharing this.

4

@gianni.zoom

Below is the response from the ticket you directed me to create during office hours (TS1838509).

Are you able to create a ticket on your end?

Our Technical Support team assists with product-level defects. We have confirmed this issue is configuration-related and not within the scope of your account’s Developer Support Plan, as such this case will be closed.

For help with developer configuration issues, custom solutions, custom integrations, or feature requests, please visit our Developer Forum where Zoom Developers and community members are available to assist you.

5

@joeyharrington this should not have been closed, but should have been routed to developer support. I am reaching out internally to get it reopened.

6

Hi @joeyharrington was this reopened for you?

7

@gianni.zoom no, it was not reopened to my knowledge

8

Having same issue here. Endpoint works for my own account’s userId & # but nobody else.

9

Hi @joeyharrington @sam8 ,

The SMS API requires a User-Level OAuth token, so the token must match the User sending the SMS. Despite having admin status, you need to use an user-level app and will have to find a way to manage the tokens from each user after authorized. You can install the app globally though through the admin portal.

I will give feedback about clarifying across our documentation which scopes/endpoints are for user-level use only.